Claude Code only knows one account at a time
The CLI uses the current identity. Nothing reminds you, on opening, that the Alice project expects client A's account, not your personal one.
Claude Code guide · 5 min
Multiple Claude Code accounts, one neatly organized history.
Personal, client, team: three Claude subscriptions, three separate bills, but always the risk of opening the wrong session on the wrong project. Here's how Tramya keeps each account siloed while giving you one unified view.
The problem
Why it's so easy to slip up.
Tokens land on the wrong invoice
A session launched under the wrong identity burns credit from the wrong account. Your contract with the client is weakened by it.
Histories get crossed
Without a marker, your personal project's history ends up holding client sessions, and vice versa. Manual sorting doesn't last more than two weeks.
The Tramya method
Four steps, once and for all.
1. Declare each account
Settings > Identities. Add "Personal", "Client Alice", "DataOps Team": each with a color.
2. Link each project
In the Projects view, select the repository and choose which Claude identity to use. The filter is remembered.
3. Check before opening
Tramya shows a red badge if you're connected to Claude Code under a different identity than the one the project expects.
4. Pick up in the right place
From an archived session: Resume → Tramya pre-checks the active identity and reopens Claude Code on the right conversation.
What Tramya doesn't do
The limits, honestly.
| Feature | Status | Detail |
|---|---|---|
| Manage Claude API keys | No | They stay in the keychain managed by Claude Code itself. |
| Switch identity inside Claude Code | No | The CLI doesn't expose it. Tramya alerts you, you run the switch. |
| Consolidate Anthropic invoices | No | Each account stays billed separately by Anthropic. |
| Separate histories by project | Yes | Automatic filter, visual badge, alert on a crossed open. |
Frequently asked questions
Can I bill a client without mixing it with my personal account?
Yes. Each project is locked to one Claude identity. You open Claude Code with the client's account for that project, and your personal account is never used for that repository.
Does Tramya store my Claude API keys?
No. Tramya only reads session metadata already present locally. The tokens stay managed by Claude Code.
How many Claude accounts can you declare?
No technical limit. On Free, one device and local use. On Pro and Cloud, as many identities as you need.