feat: support multiple accounts with identical email addresses

[lucasgsalaroli]

Description

When two Claude accounts share the same email address (e.g. a personal Pro subscription and a corporate Team/Pro seat under the same email), cux add detects the email match and updates the existing slot instead of creating a new one. This makes it impossible to register both accounts natively.

Steps to reproduce

1. Add account A (user@example.com — personal Pro) via cux add
2. Log into account B (user@example.com — corporate, different organizationUuid) via claude /login
3. Run cux add again

Expected: slot 3 created for account B
Actual: "Refreshed slot 1 (user@example.com)" — account B overwrites account A's token

Root cause

The deduplication logic in cux add uses emailAddress as the unique key. However, Anthropic's identity model allows the same email to be a member of multiple organizations, each with a distinct organizationUuid and independent rate limit windows. Two accounts with identical emailAddress but different organizationUuid are functionally separate accounts with separate tokens and separate 5h/7d usage buckets.

Secondary issue: usage cache collision

Even after manually adding the second account via filesystem/Keychain hacks, the usage cache (runtime/usage-cache.json) is also keyed by email. Both slots display identical usage metrics, making threshold-based auto-swap unreliable:

SLOT 01  user@example.com      5h: 40%  ← correct
SLOT 03  user@example.com__…   5h: 40%  ← wrong (actual: 4%)

The Anthropic usage API (GET /api/oauth/usage) is token-scoped and returns correct per-account data. The issue is the cache keying, not the API itself.

Proposed fix

Use organizationUuid (already present in oauth.json) as the deduplication key instead of (or in addition to) emailAddress. This uniquely identifies an account across all Anthropic subscription types.

The same change should apply to the usage cache key in runtime/usage-cache.json to ensure independent usage tracking per slot.

Workaround (until fixed)

1. Temporarily alias slot 1's email in state.json and rename its directory
2. Run cux add while logged into account B → creates slot 3
3. Restore slot 1's original email and directory name
4. Alias slot 3's email to email__corp in state.json, Keychain entry, and accounts directory to prevent usage cache collision

This is fragile and breaks on any cux add refresh.

Environment

• cux version: cux 0.2.5
• OS: macOS (Apple Silicon)
• Claude plan: Pro (personal) + Pro (corporate Team seat)
• Same email: yes — different organizationUuid per account

---

This issue was documented with AI assistance.

[inulute]

Hey @lucasgsalaroli — this is now fixed in v0.2.6. Here's what changed and how to test it:

---

What was fixed

Both issues you described are addressed:

1. cux add deduplication: now uses organizationUuid (already in Claude Code's local oauth.json) alongside email as the identity key. Two accounts sharing an email
   but belonging to different organizations are registered as separate slots.
2. Usage cache collision: runtime/usage-cache.json is now keyed by organizationUuid when available, so each slot tracks its own independent 5h/7d metrics.
   Threshold-based auto-switching will work correctly across same-email accounts.

---

How to test

1. Update to the latest version
2. Log into your personal account via claude /login, then run cux add → should create slot 1
3. Log into your corporate account (same email, different org) via claude /login, then run cux add → should create a new slot (e.g. slot 2), not refresh slot 1
4. Run cux list — both slots should show their own independent usage percentages
5. Trigger a threshold swap — it should correctly read usage from each slot separately

If you hit any edge cases (e.g. legacy slots behaving unexpectedly after the upgrade), let us know - slots added before this fix have no orgUuid stored, but running
cux add again on each one will backfill it.

Thanks for the detailed report - the root cause analysis and the workaround steps made this very straightforward to track down. 🙏