Repository navigation
feat: show a second Claude account as its own card - #14
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A second Claude subscription sign-in now gets its own card in the flyout, beside the main
~/.claudeone. 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
claudeAgentprovider instances, each with its ownhomePath(aCLAUDE_CONFIG_DIR). Fleet reads T3'suserdata/settings.jsonfromT3CODE_HOME(environment, then the registry), else~/.t3. It lists every enabledclaudeAgentinstance whose folder has a.credentials.json, and names the card after the instance'sdisplayName(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_claudeis now_claude_account(agent, key, config_dir). The main account keeps its existing keyclaude, so its cache, backoff and dead-token files are unchanged. Each extra account gets its own key (claude_<instance>)./usagefallback and renewal run withCLAUDE_CONFIG_DIRset to that account's folder. Fleet still never calls the token endpoint.~/.claudemay fall back to the desktop app's samples.family: "claude".Verification
test_a_key_written_to_the_windows_registry_turns_its_provider_on, also fails on unmodifiedmainon this machine. That's a real registry key leaking past the mock.CLAUDE_CONFIG_DIRClaude · Max 20xandClaude OXO · Max 5xboth read live. The offscreen render at 100% scale fits.🤖 Generated with Claude Code