Open self-serve, no waitlist. Hand this to your coding agent and it reads the spec, installs the CLI and wires the MCP server in. You authorize GitHub and restart once.
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` auto-registers Claude Code only. On any other harness it prints a
secret-free config block instead, 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 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` BEFORE `retasc bind`, or you'll create a separate org by mistake.
`retasc bind` auto-registers Claude Code only. On any other harness it prints a
secret-free config block instead, 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 device code, anything ambiguous during
bind, 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.
The CLI work, start to finish, including join if you were invited. It reads the spec, picks the commands, and reports what it changed.
Three handoffs the agent can't do for you. It stops and asks at each one, then picks up where it left off.
bind creates your org and project, mints an agent key, and wires the MCP server into this folder.
One global CLI: the MCP proxy, the keystore watchdog, and the management commands.
$ npm i -g @retasc/cliGitHub device-flow. First sign-in creates your account; the same GitHub finds your existing orgs, no duplicates.
$ retasc loginCreates your org + project, mints an agent key, wires the MCP server in, and prints your workspace id.
$ retasc bindbind wires Claude Code automatically. Anything else takes one paste of a secret-free block, safe to commit.
$ claude mcp add retasc --transport stdio \
--env RETASC_WORKSPACE=<your-workspace-id> \
-- retasc mcp-proxyretasc bind runs this for you. Add -s user to register it globally.
[mcp_servers.retasc]
command = "retasc"
args = ["mcp-proxy"]
[mcp_servers.retasc.env]
RETASC_WORKSPACE = "<your-workspace-id>"Add to ~/.codex/config.toml.
{
"mcp": {
"retasc": {
"type": "local",
"command": ["retasc", "mcp-proxy"],
"enabled": true,
"environment": { "RETASC_WORKSPACE": "<your-workspace-id>" }
}
}
}Add to opencode.json (project) or ~/.config/opencode/opencode.json.
{
"mcpServers": {
"retasc": {
"command": "retasc",
"args": ["mcp-proxy"],
"env": { "RETASC_WORKSPACE": "<your-workspace-id>" }
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
{
"mcpServers": {
"retasc": {
"command": "retasc",
"args": ["mcp-proxy"],
"env": { "RETASC_WORKSPACE": "<your-workspace-id>" }
}
}
}Cline → MCP Servers → Installed → Configure, or paste into cline_mcp_settings.json.
{
"mcpServers": {
"retasc": {
"command": "retasc",
"args": ["mcp-proxy"],
"env": { "RETASC_WORKSPACE": "<your-workspace-id>" }
}
}
}Add to ~/.gemini/settings.json.
Sign in with the same GitHub: bind lists your orgs and projects to pick from, no duplicates. Verify any session with whoami.
An owner mints a single-use invite in the Dash. Run retasc join <code> after login and you land in their org.
Hosted agents and CI authenticate with a remote key against mcp.retasc.com/mcp. See the onboarding docs.