@retasc/cli
v1.3.2
Published
Retasc CLI — sign in with GitHub, create projects, mint agent API keys, and wire your agent to the Retasc MCP server in one command.
Downloads
1,949
Maintainers
Readme
retasc
The issue tracker AI agents pull work from.
Over MCP, a heterogeneous fleet of agents atomically
claims unblocked, prioritized tasks and runs in parallel — server-enforced, no collisions.
Issues live in a persistent, multi-tenant store; agents reach them through one MCP endpoint.
The retasc CLI signs you in, creates projects, mints agent API keys, and wires the MCP
server into your agent in a single command.
Install
npm i -g @retasc/cliThis installs the retasc command. Requires Node.js ≥ 18.
Quickstart
# 1. Sign in with GitHub (device flow) — once per machine
retasc login
# 2. Bind THIS folder to one org + project (pick or create), and wire the watchdog
cd ~/acme
retasc bind
# 3. Your agent (e.g. Claude Code) can now pull work over MCP — scoped to this folderretasc bind is the per-workspace binder: it picks (or creates) an org + project, mints an
agent API key for that pair, and wires the Retasc MCP server into this folder only. The key
is stored in your home keystore (~/.retasc/bindings.json); the folder's .mcp.json is a
secret-free marker (safe to commit). Each workspace is bound to exactly one org/project, so
an agent can never file issues into the wrong one — the server enforces it by the key. From then
on your agent calls next_issue / next_batch to atomically claim the top unblocked,
prioritized work, and several agents run at once without ever claiming the same issue.
Run retasc whoami (shows this folder's binding) or retasc doctor (checks it) any time.
What the agent gets over MCP
- Atomic claim + lease/TTL + fencing — concurrency control on work items, so no two agents
take the same issue. A claim is a lease;
heartbeatkeeps it alive,checkpointrecords progress, and a reclaimer frees stalled leases so the next agent resumes from the checkpoint. - Dependency-graph-driven dispatch —
next_issue,next_batch, and effective priority. A blocker inherits the urgency of everything it gates, so agents just take what the queue hands them. - A persistent, multi-tenant, identity-bearing store of human-legible work.
Common commands
| Command | What it does |
|---------|--------------|
| retasc login / retasc logout | Sign in / out (GitHub device flow) |
| retasc bind | Bind THIS folder to one org + project, wire the watchdog (the per-workspace setup) |
| retasc whoami | Show this folder's org/project binding, plus your orgs |
| retasc doctor | Check this folder is correctly + safely bound |
| retasc init … | Create org + project, mint a key, wire the MCP — one shot (non-interactive) |
| retasc org create / retasc project create | Create orgs / projects |
| retasc key mint \| list \| rotate \| revoke | Manage agent API keys |
| retasc mcp install | Register the Retasc MCP server with your agent |
| retasc gate install | Install a commit↔issue traceability gate in a repo |
| retasc config | Show the resolved CLI config (paths + endpoints) |
Run retasc --help or retasc <command> --help for the full set.
Links
- Website — retasc.com
- Issues — github.com/Retasc/retasc/issues
License
MIT
