Skip to content

Personal & Organisation Account Shows Only One Account #26

Open

Description

@itizarsa

I have two claude subscription with org email, one is personal & another is team account.

When I login to tokenmaxx on both accounts, it shows as only one account.

$ tokenmaxx doctor
ok       bun      1.4.0  (tested 1.2+)
ok       codex    codex-cli 0.153.2  (tested 0.144.1)
ok       claude   2.1.260 (Claude Code)  (tested 2.1.206)
ok       security
running  manager daemon (0.0.65)
ok       version  0.0.65 (latest)
ok       proxy    127.0.0.1:8459
ok       codex    config.toml selects the tokenmaxx provider
ok       claude   settings.json routes ANTHROPIC_BASE_URL through tokenmaxx
note     pi       not routed — run tokenmaxx install pi
state     /Users/arshath/.tokenmaxx/state.sqlite

Activity

  1. added a commit that references this issue on Oct 2, 2026
    67b556d
  2. rubrot commented on Oct 2, 2026

    @rubrot

    Thanks for the report, and sorry for the slow reply. The cause: tokenmaxx identified a Claude account only by the user, so a personal plan and a team plan under the same login counted as one account. Signing into the second plan was treated as a re-login of the first and replaced its credential.

    #38 fixes this by identifying each account by organization plus user. Your two subscriptions become two accounts. The second one is labelled with its plan, for example you@org.com (team), so switch, logout and order can tell them apart. Accounts you already have keep working and need no action.

    If you'd like to try it before it's merged, the PR's checks publish an alpha build, and the install command is in the "try this branch" comment on #38. After installing it, run tokenmaxx login claude again for the plan that's missing. If both plans then show up, or don't, please let us know here.

  3. itizarsa commented on Oct 4, 2026

    @itizarsa
    Author

    It works on the alpha. Waiting for main release

  4. rubrot commented on Oct 4, 2026

    @rubrot

    Thanks for testing it on a real account with both plans. #38 will go into a regular release once it has been reviewed and merged, and I'll update this issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions