Skip to main content

Connect your agent to your account

Installing ChangePilot sets up session hooks (automation on each session). Connecting logs the agent into your ChangePilot workspace and binds it to your active organization.

Claude Code desktop: your agent runs changepilot-install.js connect, then you approve once at /connect-agent. That is the only human step for signed-up users.

Direct link — Claude Code approval

Send this to anyone whose agent already printed a code:

https://changepilot.deltamarksystems.com/connect-agent

With code pre-filled: add ?code=XXXX-XXXX from the agent output.

Install sets up session hooks. Connect binds your account.

changepilot-install.js install downloads hook scripts and merges them into your agent settings. It does not log you in or register an authenticated MCP server.

changepilot-install.js connect starts device flow, you approve once in the browser, and the installer writes a scoped PAT plus the Authorization header your agent needs (~71 tools, org-bound).

If your MCP menu shows Connected + Authenticated but only 6 tools, you are on the anonymous tier — not your ChangePilot account. Run connect and approve at /connect-agent.

Quick check: anon tier = 6 tools · signed-in account ≈ 71 tools

Where do I go?

Pick the situation that matches you. Every signed-up user ends at one browser approval — the agent handles the rest.

Claude Code (desktop) — I already have a ChangePilot account

Darren-class path. Your agent runs connect; you approve once in the browser. Hooks alone are not enough.

You (browser)
/connect-agent — open when your agent prints a code (or enter it there)
Your agent
node ~/.changepilot/bin/changepilot-install.js connect (Windows: node %USERPROFILE%\.changepilot\bin\changepilot-install.js connect)
Verify
node ~/.changepilot/bin/changepilot-install.js status — expect ~71 tools, not 6

Cursor — I already have a ChangePilot account

One page mints a PAT and shows copy-paste blocks for Cursor desktop or Cloud.

You (browser)
/connect
Your agent
Open /connect in your browser while logged in — approve and paste the PAT into mcp.json or Cloud Secrets
Verify
Agent can call get_my_assignments without -32001

No account yet — try before signup

Anonymous MCP tier: no login, 6 tools, plans are not persisted to your org. Enough to verify wiring.

You (browser)
/install-mcp
Your agent
POST /api/mcp/v1/auth with body { tier: "anon" } — or bare claude mcp add for discovery only
Verify
MCP lists 6 tools; create_change works within anon caps
Organization
No org binding at anon tier. After signup, run connect to bind your workspace.

No account yet — I want my work saved

Create a free account, then connect your agent with device flow (same as signed-up users).

You (browser)
/signup
Your agent
After signup: changepilot-install.js connect (Claude Code) or /connect (Cursor) — agent can also call propose_account during anon try
Verify
status shows org name; MCP shows ~71 tools

Multiple organizations — bind the right one

The agent credential is minted for your current active organization at approve time. Switch org in the app before you approve.

You (browser)
/connect-agent
Your agent
changepilot-install.js connect — but pause until the human confirms the active org below
Verify
status prints organization: <name>; briefing matches the org you intended
Organization
Use the org switcher in the app (or GET /api/set-active-org) before approving. To change later, reconnect at /connect-agent.

Connected but tools fail (-32001) or only 6 tools

Hooks or discovery-only MCP registration without a Bearer token — common partial install.

You (browser)
/connect-agent — open when your agent prints a code (or enter it there)
Your agent
node ~/.changepilot/bin/changepilot-install.js connect
Verify
node ~/.changepilot/bin/changepilot-install.js status — all lines PASS

Related