Skip to main content
Pitboard is for one person with several accounts of their own in Claude Code, OpenAI’s Codex CLI or Claude Desktop.

​
Rules

  • Pitboard switches by itself only while automatic switching is on in the app or pitboard watch is running.
  • It switches only Claude Code by itself, for the reasons in What a switch costs you and What Pitboard does not do for Claude Desktop.
  • Pitboard never sees a tool’s requests, so it never proxies or pools them.
  • Pitboard sends no model request of its own. A warm-up is Claude Code’s own request, made for an account you turned on while the app or pitboard watch runs, or for one you warm up now.
  • It decides an automatic switch from usage it has already read, never from a refused or rate-limited request. Keep the numbers fresh says how old that usage can be.
  • Pitboard renews a login a tool may be using only in the cases When Pitboard renews a login in use lists.
  • Pitboard never copies a parked login to another machine. Once one machine renews it, the other machine’s copy is spent.
  • Each machine signs in to each account itself. The Pitboard directory came from another computer covers a copied Pitboard directory.
  • Pitboard changes nothing with sudo, or as root on macOS. On Linux, root changes nothing where another user owns a folder Pitboard writes in, as Pitboard changes nothing as root says. On Windows, Pitboard changes nothing when it runs elevated. Each would leave files your own runs cannot reach.

​
What a switch costs you

Open Claude Code sessions keep the account they leave for up to about 33 seconds. Everything that runs Codex, the ChatGPT app included, keeps its account until it starts again. How open sessions follow a switch explains both. On macOS, a Claude Desktop switch needs Claude closed: Switch accounts says how. An automatic switch would miss the codex session it was meant to keep going, so Pitboard never switches Codex by itself. Restart what runs Codex lists what to restart.

​
Is this allowed

Pitboard moves only logins you already hold, between its own store and the place each tool reads them. It has no way to share an account between people. Anthropic’s and OpenAI’s terms decide whether you may use several subscriptions this way. Pitboard does four things those terms may cover:
  • It keeps Claude Code’s and Codex’s logins in its own store and renews them.
  • It sends their tokens to Anthropic and OpenAI itself, as What leaves your machine lists.
  • Automatic switching moves Claude Code to another account before a limit runs out.
  • A warm-up sends a request on a schedule to start an account’s five-hour period.
As read on 23 October 2026:
  • Anthropic’s Authentication page shows how to stay signed in to several accounts at once, “such as work and personal accounts”.
  • Anthropic’s Legal and compliance page says Pro and Max limits “assume ordinary, individual usage”. It says third-party developers “may not collect, store, or intermediate Claude.ai credentials or session tokens”.
  • From 12 November 2026, Anthropic’s Usage Policy forbids creating multiple accounts “to avoid detection, circumvent product guardrails”. It also forbids bypassing “capabilities, restrictions, or guardrails established within our products” without “prior authorization from Anthropic”.
  • Each seat of a Team plan is for one named individual, and users “can’t route their work through another user’s account to use that user’s remaining usage”.
  • OpenAI’s Terms of Use, in their EU text, forbid circumventing “any rate limits or restrictions”. Its Services Agreement, for Business and Enterprise workspaces, forbids configuring the services “to avoid Usage Limits”. Both were read in the copies Open Terms Archive keeps.
Neither names a tool like Pitboard. Whether either counts what Pitboard does under these terms is not known. A claude.ai account window signs in on claude.ai’s own pages. On macOS, WebKit keeps the sign-in’s cookies under Pitboard’s bundle identifier, and on Windows, WebView2 keeps them in Pitboard’s app data folder. A Claude Desktop switch renames Claude’s files, its session cookie among them, into a folder of Pitboard’s and back. Whether Anthropic counts either under those terms is not known.

​
Tools and sign-ins Pitboard does not support

  • Gemini CLI. Since 18 June 2026, Google no longer offers Gemini CLI’s Login with Google to individual, Google AI Pro and Google AI Ultra accounts. Google says so in Gemini Code Assist consumer accounts.
  • Windows older than Windows 11 24H2, build 26100. Pitboard reads there and refuses every change with system_too_old. Windows Server 2025 meets the floor.
  • Claude Code and Codex inside WSL, from Pitboard on Windows. Pitboard’s Linux build, run inside WSL, switches them, as Install inside WSL says. A Codex there that uses the Windows Codex home shares its login with Codex on Windows.
  • Claude Code with CLAUDE_CODE_CUSTOM_OAUTH_URL set. Its login then sits under a name Pitboard does not read. Custom OAuth endpoint lists what Pitboard refuses.
  • Claude Code set to use ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, CLAUDE_CODE_OAUTH_TOKEN, apiKeyHelper, an Anthropic profile, a third-party provider or a Cloud gateway that managed settings require. Its sessions ignore the login Pitboard switches. Variables that override the login lists them all.
  • A Claude Code account of an organisation that a managed forceLoginOrgUUID leaves out. Claude Code refuses its login, and Pitboard refuses to switch to it with login_restricted.
  • Signing in to Claude Code where managed settings set forceLoginMethod to console. Before you add a Claude Code account says why.
  • Codex signed in with an API key rather than ChatGPT.
  • A Codex account that forced_login_method, forced_chatgpt_workspace_id, allowed_login_methods or allowed_chatgpt_workspaces rules out. Codex signs out of its login or leaves it unused, and Pitboard refuses with login_restricted. Codex settings rule out an account says what to change.
  • Codex keeping its login anywhere but its file store, auth.json: in a keychain, in the Secret Service, in Credential Manager, in its encrypted secrets store or in memory. Codex keeps its login outside its file store says what to change.
  • Claude Desktop on Windows and Linux.
  • A third-party deployment of Claude, which runs from Claude-3p, as read in Claude 3.6556.2, and Claude’s own account switcher, as read in 2.7032.0. Pitboard moves no login while Claude’s cookie store holds two sessions of one name.
  • Changes from a sign-in over SSH with a key on Windows, which reaches no Credential Manager and may not reach the key that seals Pitboard’s parked logins. When the store cannot be reached says what Pitboard does.
  • Google sign-in in an account’s window, and passkeys there on macOS. Sign in gives the ways that work.