Skip to content

feat: show a second Claude account as its own card - #14

Merged
okisooo merged 1 commit into
mainfrom
feat/claude-accounts
Nov 1, 2026
Merged

okisooo merged 1 commit into
mainfrom
feat/claude-accounts

Conversation

@okisooo

@okisooo okisooo commented Nov 1, 2026

Copy link
Copy Markdown
Owner

What

A second Claude subscription sign-in now gets its own card in the flyout, beside the main ~/.claude one. Claude plans also name the Max size (Max 20x, Max 5x), so two Max accounts can be told apart.

How it finds the account

T3 Code runs extra Claude accounts as claudeAgent provider instances, each with its own homePath (a CLAUDE_CONFIG_DIR). Fleet reads T3's userdata/settings.json from T3CODE_HOME (environment, then the registry), else ~/.t3. It lists every enabled claudeAgent instance whose folder has a .credentials.json, and names the card after the instance's displayName (Claude OXO). Fleet skips an instance that is off, has no home folder, or is signed in to the same account (oauthAccount.accountUuid) as ~/.claude.

Collection

  • api_claude is now _claude_account(agent, key, config_dir). The main account keeps its existing key claude, so its cache, backoff and dead-token files are unchanged. Each extra account gets its own key (claude_<instance>).
  • The Claude Code /usage fallback and renewal run with CLAUDE_CONFIG_DIR set to that account's folder. Fleet still never calls the token endpoint.
  • Only ~/.claude may fall back to the desktop app's samples.
  • Extra accounts are paced like the main one (180 s) and polled side by side with the other local providers.
  • The panel uses the Claude icon and per-model weekly labels for any reading tagged family: "claude".

Verification

  • 332 unit tests. The only failure, test_a_key_written_to_the_windows_registry_turns_its_provider_on, also fails on unmodified main on this machine. That's a real registry key leaking past the mock.
  • New tests cover:
    • discovery: same-account, disabled, missing-login and non-Claude instances are skipped
    • name clashes
    • separate cache and backoff files
    • the CLI getting CLAUDE_CONFIG_DIR
    • no desktop fallback for extra accounts
    • Max size naming
    • the panel card
  • Running live as local build 0.4.2.3: Claude · Max 20x and Claude OXO · Max 5x both read live. The offscreen render at 100% scale fits.

🤖 Generated with Claude Code

T3 Code runs extra Claude accounts as Claude Agent instances, each with its
own CLAUDE_CONFIG_DIR. Fleet now finds them in T3's settings (T3CODE_HOME,
else ~/.t3) and reads each login like ~/.claude, named after the instance,
with separate cache, backoff and dead-token files. Claude Code's /usage
fallback runs with that account's config folder. One signed in to the same
account as ~/.claude is skipped, and only ~/.claude may fall back to the
desktop app's samples.

Claude plans name the Max size ("Max 20x", "Max 5x") so two Max accounts
can be told apart.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@okisooo
okisooo merged commit b0f8bb6 into main Nov 1, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant