Connect a work and a personal Claude (or Codex) account side by side. Pin any session to whichever plan should pay for it, watch both gauges at once, and when one runs hot, switch and keep going - the session never breaks stride. Logins stay isolated; work credentials never mix with personal. Continuum itself is free (BYOK); optional hosted inference is separate.
Every new session takes an account pin: Default, work, or personal. The session bills the plan you pinned it to - and each account keeps its own gauge, so you always know which window you're spending.
Logins are isolated by config directory. Your work credentials never mix with personal - different config dirs, different keychain partitions, no HOME swap.
The same heavy workload on a metered API key bills every token - and the meter never stops. A second flat-rate subscription is $200/mo, flat, and gives you a whole second set of windows.
Past a few heavy days a month, the second subscription is the cheaper line item - and there's no overage bill waiting at the end of it.
every token billed · the meter never stops
a whole second set of windows · already paid for
Past a few heavy days a month, a second subscription pays for itself.
Each account gets its own live gauge - usage, weekly cap, and an independent reset countdown. When work is at 87% and personal is at 12%, you can see it at a glance and move the next session to the fresh window.
Hover any account to see today's spend for that plan alone.
claude · 2 accountsindependent windowsShort answers here, long answers in the docs.
Each account authenticates with its own login through the provider's own CLI - you're using plans you pay for, exactly as you'd run them in a terminal. Continuum never proxies or shares credentials between accounts.
No. Each account gets an isolated config directory and its own keychain partition. It's a config-dir isolation model, not a HOME swap - spawn resolution is fail-closed, so a pin never silently bills the wrong plan.
Claude and Codex today. Add a secondary account in Settings, and each account gets its own gauge, its own history, and per-session pinning.
You toggle the account and keep working - the session continues. This is a manual switch, not automatic mid-turn failover: when one window runs hot, you move to the other and pick up where you left off.
Add a second account in Settings and pin your next session to it.
isolated logins · as much compute as you own