Replies: 1 comment 1 reply
-
|
Hey, great idea! Multi-profile support would be a huge usability boost for people juggling multiple accounts. One thing to consider: handling token revocation across profiles – each profile should have independent logout/revoke flow. But overall, this seems like a clean, backward-compatible addition. Good luck with the PR! :) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Today, /login stores a single token per provider in auth.json — "anthropic", "openai", etc. If you have two
accounts (e.g. a personal Claude Max and a work subscription), you have to re-authenticate every time you switch,
since the second login overwrites the first.
It would be useful to support named profiles so you can store multiple credentials per provider and switch between
them without going through the OAuth flow again.
Proposed UX
The active profile would show in the footer alongside the model name, so it's always visible.
auth.json shape
{ "anthropic": { "type": "oauth", ... }, ← existing default, untouched "anthropic:work": { "type": "oauth", ... }, "anthropic:personal": { "type": "oauth", ... } }Backward compatibility
Existing auth.json files and the plain /login flow work exactly as today. Profiles are purely additive.
Scope
The core change is a ~40-line addition to AuthStorage (a resolveStorageKey helper that checks activeProfiles from
settings before looking up auth.json). The rest is UI wiring in the OAuth selector and a new /profile command.
Happy to put together a PR if this direction sounds good.
Beta Was this translation helpful? Give feedback.
All reactions