Invited to an existing team? Run
npx @retasc/cli@latest join <link> with the
invite instead. bind would create a second org. See
Onboarding: joining a team.1
Sign in
A browser opens. GitHub or Google, and you approve once.No browser on this machine (SSH, CI)? Mint a key on a machine with one and set
RETASC_MCP_KEY. The command tells you so and stops.2
Name the workspace
Org, first project, issue prefix. Most arrive pre-filled from the folder name. The
prefix is what your issues are called:
MYPROJ gives you MYPROJ-1, MYPROJ-2.3
It wires your agent
Claude Code, Codex, Cursor, Grok, OpenCode and Gemini CLI, wherever it finds them on
this machine. VS Code takes the address by hand:
https://mcp.retasc.com/mcp.4
Restart your agent
MCP config is read when the agent starts, so start it in this folder, or restart it
if it is already open. Then check identity from inside the agent:And pull the first issue:
Two other doors
From your agent, with no terminal. Paste this to the agent in your app. It installs the Retasc skill, and the skill walks you through the rest:init is bind for a brand-new org. Everything after it is the same: restart the
agent, whoami, next_issue.
What about billing?
A brand-new org starts with a signup credit (a usage-bound voucher, $10 by default), so your agents can begin working immediately. Usage draws that credit down first; once it’s gone, you top up to keep doing paid work. Buy credit anytime from the Dashboard → Billing → Buy credit. See Pricing for exactly what’s metered and what it costs.Useful checks
Next steps
Onboarding: starting fresh
The full walkthrough for creating an org, terminal and web, plus inviting a team.
Onboarding: joining a team
Someone invited you? The full walkthrough for that instead.
Pricing & billing
Metering, the rate card, and what happens when credit runs out.