Tag Team — Account Switcher for Claude Code

Share one machine, keep separate Claude Code logins. Save each person's account once, then hand the machine over with a single click: switch from the status bar or the sidebar. Only the login changes. Settings, plugins, MCP servers, skills and history in ~/.claude stay shared.

Not affiliated with Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic, PBC. This extension manages the login files that Claude Code already stores on your machine.

Available in English and Brazilian Portuguese (follows your VS Code display language).

Features

• One-click switching from the status bar or the Tag Team sidebar. Ctrl+Alt+A (⌘⌥A) opens the list, and Ctrl+Alt+Shift+A (⌘⌥⇧A) switches back to the previous account.
• "Who is using Claude Code?" When VS Code opens, or when someone comes back after a while away, Tag Team asks which account to use, so nobody works on someone else's account by accident.
• Add an account without logging anyone out. The extension runs claude auth login and saves the new account when the browser login finishes.
• Usage limits per account: the 5-hour session window and the weekly window (plus weekly Opus/Sonnet when your plan has them), with live reset countdowns and a 7-day chart of time used on the machine.
• Usage alerts at 80% and 95%, plus a notice when the 5-hour window frees up. When your account is at its limit, Tag Team can suggest another account of the same person. It never suggests a teammate's account: rotating other people's accounts to dodge limits goes against Anthropic's terms.
• PIN and auto-lock: switching to a PIN-protected account asks for the PIN. After 30 minutes away from every VS Code window, the account locks itself, and Claude Code stays logged out until someone unlocks it.
• Private history per account (optional): conversations (/resume), prompt history, checkpoints, plans and todos become separate per account. Nothing is deleted, and turning it off brings the history back.
• Close stale sessions: an open Claude Code session keeps the previous account and can write it back when it refreshes its token. Tag Team can close those sessions for you, and it detects and repairs a swapped login.
• Per-project account: a folder can prefer an account, and Tag Team suggests switching when you open it.
• Diagnostics: one command checks the keyring, files, endpoints and versions, and produces a report with no tokens and masked emails.
• Optional keep-alive (experimental, off by default): renews idle accounts' logins before they expire.

Getting started

1. With your account logged in to Claude Code, run Tag Team: Salvar conta atual (save current account).
2. For a teammate, run Tag Team: Adicionar conta (add account). They sign in in the browser, and the account is saved.
3. Click the account in the status bar, use the sidebar, or press Ctrl+Alt+A.
4. Optional: Set PIN on your account, Set owner on each account, and Turn On Private History per Account.

The Get started with Tag Team walkthrough (Help → Welcome) shows the same steps.

Don't use /logout to switch: it can revoke the saved token on the server.

How it works

• What an account is: the file ~/.claude/.credentials.json (or the macOS Keychain item Claude Code-credentials) plus the oauthAccount field of ~/.claude.json. CLAUDE_CONFIG_DIR is respected.
• Where tokens are kept: in VS Code's SecretStorage (your OS keyring). In ~/.claude.json only oauthAccount is modified, and a backup of the previous state is kept in ~/.claude.json.switcher-bak.
• Token rotation: Claude Code rotates refresh tokens. Tag Team updates the saved snapshot of the active account whenever the files change.
• Identifying accounts: to tell same-organization accounts apart, and to read usage limits, Tag Team calls api.anthropic.com/api/oauth/profile and /api/oauth/usage. These are the same endpoints Claude Code uses.

Keep-alive (experimental)

Refresh tokens last about 30 days. The active account is refreshed by Claude Code itself. With tagTeam.keepAlive.enabled on, Tag Team checks every hour and renews idle accounts that are within 7 days of expiring (tagTeam.keepAlive.renewDaysBefore).

• A file lock stops two VS Code windows from renewing the same account at the same time.
• Renewal uses Claude Code's own OAuth endpoint and client ID. That is not a public API, and Anthropic may consider it unauthorized use. Enable it at your own risk.

Settings

Platforms

Security notes

• PIN: the PIN is a convenience lock for people sharing a machine. It does not protect against someone using the same OS user, because the tokens stay in the keyring and in ~/.claude.
• Network: the extension only talks to api.anthropic.com, plus platform.claude.com when keep-alive is on. It has no telemetry.

Development

npm install
npm test          # unit tests (vitest)
npm run test:e2e  # end-to-end tests in a real VS Code, against a fake Claude config dir
npm run l10n:export  # refresh l10n/bundle.l10n.json after adding strings; add the pt-BR text to bundle.l10n.pt-br.json
npm run package   # typecheck + tests + .vsix

Releases are published by GitHub Actions on every push to main whose package.json version is not on the Marketplace yet:

npm version patch --no-git-tag-version   # bump version
git commit -am "Release 0.6.1" && git push
# CI tests, publishes to the Marketplace, tags vX.Y.Z and attaches the .vsix to a GitHub Release