OSS · Chrome Extension · Node.js

claude-shift

One machine, many Claude Code accounts.

Manages multiple Claude Code logins on the same box. shift use swaps the active account by syncing the two files Claude Code actually reads (~/.claude/.credentials.json for tokens, ~/.claude.json for the oauthAccount /status displays). A local API server polls api.anthropic.com/api/oauth/usage and snapshots 5-hour and weekly utilization to SQLite. A Chrome popup shows every account with a cross-account SVG line chart — and lets you switch active from the popup, not just read.

View on GitHub Two-file auth internals →

Terminal demo of claude-shift: shift list prints three registered accounts with the active one marked, shift usage reports 5-hour and weekly percentages with reset times per account, shift use imoto-team switches active and the next list confirms the new active flag.
shift list → shift usage → shift use → shift list. Every switch syncs back the refreshed token and rewrites the oauthAccount /status reads, so login stays valid and the display stays truthful.

CLI commands

One shell script over Node helpers. Every command works standalone; server and popup are optional.

Command What it does
shift list List every registered account and mark the active one.
shift use <name> Swap the active account. Syncs back the refreshed token and updates oauthAccount in ~/.claude.json.
shift usage Print 5-hour and weekly percentages with reset times for every account.
shift seed <name> Start the 5-hour window with a minimal billed request. Useful right before a long session.
shift add <name> Register the current credentials.json as <name>. Duplicate tokens warn (-f to force).
shift rm <name> Delete the account registration. Removing the active one requires -f.
shift server Start the local API server on 127.0.0.1:19867. Polls usage on an interval and snapshots to SQLite.

Chrome popup

The popup talks to a local server on 127.0.0.1:19867 that polls the usage API on a configurable interval and snapshots results to SQLite. Every account gets a 5-hour and weekly bar; the analytics modal draws a cross-account SVG line chart over 6h / 24h / 7d. The active card carries a 使用中 badge; the others show a 切替 button that calls the same shift use pipeline underneath.

Claude Shift Chrome popup showing three accounts (imoto-max20 at 98% weekly in red, imoto-team at 51% weekly in blue, kumiko active at 9% weekly), with 5-hour and weekly bars per account and reset times.

Install

Clone the repo and register accounts one at a time. Each account is captured right after /login inside Claude Code.

# 1. Clone and install
git clone https://github.com/kenimo49/claude-shift
cd claude-shift
npm install
chmod +x shift.sh

# 2. Register accounts, one at a time
# Inside Claude Code, run /login for the account you want to register.
# Immediately after, register it:
./shift.sh add my-account-a

# Repeat /login + add for every account you want to manage.

# 3. Start the usage server (optional, needed for popup)
./shift.sh server --interval 5

# 4. Load the Chrome extension
# chrome://extensions → Developer mode → Load unpacked → extension/

Four things worth knowing

Each of these took a real incident to surface. Documented so the next reader skips them.

  1. The account display is in ~/.claude.json, not the credentials file

    Swapping only ~/.claude/.credentials.json leaves /status showing the previous account while the new token authenticates every request. The mismatch is silent and confusing. shift use fetches the profile from api.anthropic.com/api/oauth/profile with the new token and writes both files consistently.

  2. Refresh tokens must be synced back before overwriting

    The token file on disk is refreshed by Claude Code during a session. Overwriting it with the target account without syncing the current file back to its own account slot throws that refresh away and can require re-login. shift use sync-writes the current credentials into the previously active account slot before replacing them.

  3. The 5-hour window starts on first use, not on the wall clock

    Two Max/Team accounts started at 10:00 and 15:00 give you two independent 5-hour windows you can chain. shift seed forces a tiny billed request to start the window on demand, so you can position a fresh window right before a long session.

  4. The popup polling interval is configurable, and persists

    The server accepts --interval N (minutes) at start and a POST /config from the popup. The value is written to ~/.claude-shift/config.json and reloaded on the next tick. Default 10 minutes; the popup gear icon changes it live without restarting the server.

Related developer tools

All products →

← Back to products