Wire it into the queue over MCP so it can pull work and start shipping. One command, interactive, for a developer starting from a terminal with no invite yet. Joining a team, or working from a browser instead? The routing below sends you to the right page, terminal and web, either way.
It's interactive: sign in, name your org, say where your work comes from, done.
$ npx @retasc/cli bindChoose GitHub or Google, then approve it in your browser. It remembers which one you picked next time.
Type a name. Straight to this if you don't have one yet.
Pick a tracker to bring across (Linear, Jira, ClickUp, Asana, Shortcut), or start fresh and let your agents file into it.
Keep retasc on your machine, or run it on demand every time. Your call.
Nothing else to type. The folder's wired and the key's minted. Restart your agent and it pulls from the queue.
Rather your agent do all of it? No terminal, no clicking, no commands to type or paste yourself: hand it one prompt and it runs the setup, stopping only for the parts only you can do.
Every combination of audience and track lives in the docs, in full: real screens for the web track, real terminal output for this one.
It reads llms.txt, the same spec it will use to pull work, and stops for the parts only you can do.
Onboard me onto Retasc: read https://retasc.com/llms.txt, follow its setup path,
install the CLI, sign me in, and bind this folder to a new org and project.
`retasc bind` wires the Claude Code CLI automatically. On any other harness it
always also prints a secret-free config block, so put that block in your own MCP
config and tell me which file you changed.
Stop and ask when you need me: I authorize the GitHub or Google device code in my
browser, I choose the org and project names, and I restart this session at the
end so the MCP server loads.Onboard me onto my team's Retasc org. My invite code: <PASTE CODE>
Read https://retasc.com/llms.txt, follow its join path, and redeem the code with
`retasc join <code>`, one command: it signs me in, redeems the invite, and
binds this folder to the org I joined. Don't also run `retasc bind` afterward,
the folder's already bound and a second bind will refuse.
`retasc join` wires the Claude Code CLI automatically. On any other harness it
always also prints a secret-free config block, so put that block in your own MCP
config and tell me which file you changed.
Stop and ask when you need me: the GitHub or Google device code, anything
ambiguous during setup, and a restart at the end so the MCP server loads.Paste your code into the first line. An owner mints it in the Dash under Team → New invite, or with retasc members invite.