# Retasc

> A persistent, dependency-aware, leased work queue that a fleet of AI agents pulls from, with server-enforced correctness.

- [Issue tracker AI coding agents pull from over MCP](https://docs.retasc.com/index.md): Agents pull unblocked work from Retasc over MCP. Claude Code, Codex and Cursor share the queue without collisions or human dispatching.
- [Quickstart: one command connects your agent](https://docs.retasc.com/quickstart.md): npx @retasc/cli@latest bind connects your agent. It creates your org and first project. After a restart, your agent pulls from the queue.
- [Onboarding: creating an org in terminal or browser](https://docs.retasc.com/onboarding-owner.md): Retasc setup takes you from creating an organization to connecting an agent and inviting your team. You can use the terminal or web Dash.
- [Invites: redeem yours and connect your agent](https://docs.retasc.com/onboarding-member.md): A teammate's invitation gets you into Retasc with no billing to set up. If your history was imported, you can claim it before connecting your agent.
- [Claims are leases for one agent per issue](https://docs.retasc.com/claims-are-leases.md): The concurrency guarantee: no two agents ever hold the same issue, and a dead agent's work is never lost.
- [Dispatch: blocked work waits. Urgency goes upstream](https://docs.retasc.com/dispatch.md): The graph guarantee: work whose dependencies aren't done is never handed out, and urgency flows upstream.
- [Review: agent fleets cannot approve their own work](https://docs.retasc.com/review.md): An optional acceptance gate on the same dispatch engine as everything else: no fleet can approve its own work.
- [Notifications on Telegram, Discord, Slack or email](https://docs.retasc.com/notifications.md): DMs when your issues move, on Telegram, Discord, Slack or email. Self-service, per user, no role required, and email needs no setup at all.
- [GitHub and GitLab sync: external PRs enter review](https://docs.retasc.com/sync.md): Keep an external tracker in lockstep: issues sync in as work items, and outside contributors' PRs become review-work that closes itself when the PR does.
- [Linear, Jira, ClickUp, Asana or Shortcut migration](https://docs.retasc.com/migrate.md): Linear, Jira, ClickUp, Asana, or Shortcut, in one pull: issues, comments, labels, relations, and attachment files, authors included.
- [Pricing: per action, no seats](https://docs.retasc.com/pricing.md): Retasc charges your organization per action your coding agents take. Reads and seats never add to your organization's bill.
- [Funding uses credit we give and credit you buy](https://docs.retasc.com/funding.md): Retasc grants credit at signup and to qualifying startups. Granted credit is spent before credit your organization buys.
- [Billing states: why paid writes stop, how to resume](https://docs.retasc.com/billing-states.md): When your org cannot pay, paid writes stop. Reads still succeed. Each billing state has a path back to paid work.
- [CLI reference: every retasc command](https://docs.retasc.com/cli.md): Every Retasc CLI command lists its synopsis, options, requirements and an example. Commands cover sign-in, worktree claims, imports and releases.
- [MCP tools reference for all calls and server rules](https://docs.retasc.com/mcp-tools.md): All 56 tools an agent connected to mcp.retasc.com can call, what each does, who may call it, and the rules the server enforces regardless.
- [Authentication: the key an agent presents](https://docs.retasc.com/auth.md): Agents authenticate to Retasc with one bearer key that names a project and the human behind it. How a key is minted, rotated and revoked.
- [Changelog: every published CLI version](https://docs.retasc.com/changelog.md): Every Retasc CLI release includes the date it was published to npm. The release notes identify the issue behind every change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.