GetResolved
Getting started

Quick Start

The fastest way to use GetResolved is from your editor.

Markdown

Command-line usage with Claude Code is the most efficient way to work with GetResolved. The CLI installs a /get-resolved slash command so you can list, update, and resolve issues without leaving your editor.

1. Install and run

In your project root:

bash
npm install -g @getresolved/cli
getresolved

First-time users with no global auth are dropped straight into the setup flow: log in (browser device-code), pick or create a product, and install the /get-resolved slash command at ~/.claude/commands/get-resolved.md. A small .getresolved/config.json records the product link in this directory — no secrets, safe to commit.

Requires Node.js 18+.

2. Use it from Claude Code

In any Claude Code session, type /get-resolved followed by your request:

text
/get-resolved list my open issues
text
/get-resolved please fix issue GET-123

See the Claude Code integration page for more examples.

What's next

Built for vibe coders and solo founders.

Try Free

No credit card required

GetResolved

Issues

TitlePriority
ACME-214Signup verification redirects back to email step
Urgent
ACME-218Webhook retries failing on upstream 5xx
Urgent
ACME-220Rate limit dashboard CSV exports to 5/min
High
ACME-198Include custom fields in CSV contact export
Normal
ACME-205Bulk-resolve from the inbox list
Normal
ACME-207Daily Slack digest of unresolved high-priority issues
Normal
ACME-211Improve chat widget cold-start performance
Normal
ACME-219Reorder columns in the contacts table
Low
ACME-216Email digest of resolved issues for stakeholders
Low
ACME-203Add a dark mode toggle to the dashboard header
Low