Claude Code subscription
Routeplane can adopt the Claude Code CLI’s live Pro or Max session under the dedicated claude-code provider. It does not copy the token into Routeplane; it stores a marker and reads the current Claude Code credential live.
Log in
Section titled “Log in”routeplane providers login claude-code --label personalIf the Claude CLI already has a live session, Routeplane adopts it. Otherwise the command starts claude auth login --claudeai. Routeplane stores the non-secret session marker under $XDG_DATA_HOME/routeplane/oauth-tokens.json.
routeplane providers logout claude-code # removes every stored label for this providerMultiple accounts
Section titled “Multiple accounts”Add the chosen label to routeplane.yaml, then reload:
providers: claude-code: account_strategy: failover accounts: - label: personalrouteplane reloadVerify it
Section titled “Verify it”First verify that the daemon resolves the subscription route:
routeplane route claude-code:claude-sonnet-4-6That proves routing configuration, not account capacity. Prove the real path with Claude Code itself:
routeplane spawn -a claude -- -p "Reply with one short sentence."Check routeplane insight --since 10m for the provider and account label. A 429 proves the request reached the subscription provider but also proves that the account is currently capacity-blocked; only an ok record proves a usable turn.
Learn more
Section titled “Learn more”- Claude Code — point the Claude Code CLI at Routeplane.
- Insight — inspect content-free local outcome records.
- Models — the provider/model id scheme.