Skip to main content

Enroll with your coding agent

The link your admin sent is also a prompt. Paste it into Claude Code or Codex and say "enroll me".

1
Paste the link and say enroll me

Paste the enrollment link into Claude Code or Codex, then add "enroll me".

https://app.anyray.ai/i/enl_7f3a9c2e enroll me

The agent reads its own instructions from the link and runs the enrollment.

2
Sign in, if the agent shows you a link

On SSO the agent prints a sign-in URL. Open it in any browser, on any machine, and sign in. The agent waits, then carries on. Without SSO nothing opens.

3
Read the report

The agent lists every tool it set up and says which editors need a restart.

You're enrolled

The agent's doctor report shows the gateway reachable and each tool routed, and your admin sees you on the console's Users page.

What the agent actually does

Every enrollment link has a runbook behind it, written for agents: https://app.anyray.ai/i/<code>/agent.md, where <code> is the enl_… or tnt_… part of your link. Fetching /i/<code> with Accept: text/markdown returns the same text. The runbook tells the agent to run the enrollment command detached, with --json appended:

curl -fsSL https://app.anyray.ai/i/<code> | sh -s -- --json

Connect then streams NDJSON events instead of prompting. sso_grant carries the sign-in URL the agent hands you; enrolled and applied report the identity and the per-tool results; error names what went wrong. The full event contract is on the CLI commands page. The agent finishes with anyray-connect doctor --json and reports from that.

Your key never appears in the transcript: Connect mints it on your machine and stores it with owner-only permissions, the events carry identity and tool names only, and the runbook forbids printing keys, editing tool configs by hand, and sudo. A devcontainer or SSH host works the same way; see remote and ephemeral machines.