4.4 KiB
summary, read_when
| summary | read_when | ||||
|---|---|---|---|---|---|
| OAuth in Clawdbot: token exchange, storage, and multi-account patterns |
|
OAuth
Clawdbot supports “subscription auth” via OAuth for providers that offer it (notably OpenAI Codex (ChatGPT OAuth)). For Anthropic subscriptions, use the setup-token flow. This page explains:
- how the OAuth token exchange works (PKCE)
- where tokens are stored (and why)
- how to handle multiple accounts (profiles + per-session overrides)
Clawdbot also supports provider plugins that ship their own OAuth or API‑key flows. Run them via:
clawdbot models auth login --provider <id>
The token sink (why it exists)
OAuth providers commonly mint a new refresh token during login/refresh flows. Some providers (or OAuth clients) can invalidate older refresh tokens when a new one is issued for the same user/app.
Practical symptom:
- you log in via Clawdbot and via Claude Code / Codex CLI → one of them randomly gets “logged out” later
To reduce that, Clawdbot treats auth-profiles.json as a token sink:
- the runtime reads credentials from one place
- we can keep multiple profiles and route them deterministically
Storage (where tokens live)
Secrets are stored per-agent:
- Auth profiles (OAuth + API keys):
~/.clawdbot/agents/<agentId>/agent/auth-profiles.json - Runtime cache (managed automatically; don’t edit):
~/.clawdbot/agents/<agentId>/agent/auth.json
Legacy import-only file (still supported, but not the main store):
~/.clawdbot/credentials/oauth.json(imported intoauth-profiles.jsonon first use)
All of the above also respect $CLAWDBOT_STATE_DIR (state dir override). Full reference: /gateway/configuration
Anthropic setup-token (subscription auth)
Run claude setup-token on any machine, then paste it into Clawdbot:
clawdbot models auth setup-token --provider anthropic
If you generated the token elsewhere, paste it manually:
clawdbot models auth paste-token --provider anthropic
Verify:
clawdbot models status
OAuth exchange (how login works)
Clawdbot’s interactive login flows are implemented in @mariozechner/pi-ai and wired into the wizards/commands.
Anthropic (Claude Pro/Max) setup-token
Flow shape:
- run
claude setup-token - paste the token into Clawdbot
- store as a token auth profile (no refresh)
The wizard path is clawdbot onboard → auth choice setup-token (Anthropic).
OpenAI Codex (ChatGPT OAuth)
Flow shape (PKCE):
- generate PKCE verifier/challenge + random
state - open
https://auth.openai.com/oauth/authorize?... - try to capture callback on
http://127.0.0.1:1455/auth/callback - if callback can’t bind (or you’re remote/headless), paste the redirect URL/code
- exchange at
https://auth.openai.com/oauth/token - extract
accountIdfrom the access token and store{ access, refresh, expires, accountId }
Wizard path is clawdbot onboard → auth choice openai-codex.
Refresh + expiry
Profiles store an expires timestamp.
At runtime:
- if
expiresis in the future → use the stored access token - if expired → refresh (under a file lock) and overwrite the stored credentials
The refresh flow is automatic; you generally don't need to manage tokens manually.
Multiple accounts (profiles) + routing
Two patterns:
1) Preferred: separate agents
If you want “personal” and “work” to never interact, use isolated agents (separate sessions + credentials + workspace):
clawdbot agents add work
clawdbot agents add personal
Then configure auth per-agent (wizard) and route chats to the right agent.
2) Advanced: multiple profiles in one agent
auth-profiles.json supports multiple profile IDs for the same provider.
Pick which profile is used:
- globally via config ordering (
auth.order) - per-session via
/model ...@<profileId>
Example (session override):
/model Opus@anthropic:work
How to see what profile IDs exist:
clawdbot channels list --json(showsauth[])
Related docs:
- /concepts/model-failover (rotation + cooldown rules)
- /tools/slash-commands (command surface)