How do you manage multiple Claude subscriptions in one place?
Short answer
Put every account on one board that reads its usage. Orpheus shows each Claude subscription's weekly and 5-hour usage, when each resets, what it is on track for by the reset and when it will run out. You can move an idle agent to the account with room, or turn on Auto-move and alerts so it happens before an account runs out.
On this page
Why it is hard by hand
Each Claude subscription has its own 5-hour and weekly limit, and Claude Code shows them one account at a time with /usage.1 With two or more accounts signed in on different config folders and machines, you have to check each one, and you tend to find out an account is empty when an agent on it stalls. Running several accounts on one machine is covered in how to run two Claude accounts on one machine. This guide is about keeping track of them once they run.
What to watch for each account
| Reading | What it tells you |
|---|---|
| Week used | The share of the weekly limit used so far, and when the week resets |
| On track for | Where the week will end at the current pace, for example "On track for 118% by reset" |
| Runs out | The time the account will hit its limit, shown when that is before the reset |
| Burn trend | A chart of this week's use, day by day, with the limit line and the projection to the reset |
| Current session | The share of the 5-hour limit used, and when it resets |
| Agents | Which agent sessions run on the account, and which are idle |
"On track for" matters more than "used". An account at 60% on Tuesday can be on pace to run out on Thursday, while one at 80% the day before its reset is fine.
Put your accounts on one board
-
Give each account its own config folder
Sign in each subscription once in its own folder, then start each agent in tmux with the folder of the account it should use.2
CLAUDE_CONFIG_DIR=~/.claude-work claude -
Connect each machine
Paste the setup prompt to an agent on the machine. It installs the connector, which finds the Claude logins there and reads their usage.3
-
List the logins in the policy file
Add each config folder to
loginsin the connector's local policy file. Only accounts listed there can take an agent that is moved.2 -
Open Usage
Every account gets a card with the readings above. Accounts past your plan's limit stay locked until you change plan.
Move agents between accounts
Tap an idle Claude session on Usage and choose "Move to another account". The list shows each account's week and what it is on track for, so you pick with the numbers in front of you. Orpheus restarts the agent in the same tmux pane and folder under the other account with claude --continue, so the conversation carries on.2
Only idle sessions can move, and only to an account signed in on the same machine and listed in its policy file. Moving needs a plan with 2 or more Claude accounts.4
Turn on Auto-move
Auto-move is off until an admin turns it on at the top of the Usage page. The first time, Orpheus shows what it does and what Anthropic's terms say about using several accounts.
- When it moves: an account reaches your threshold of its week (80, 85, 90 or 95%, 90% by default), or is on track to run out before it resets.
- What it moves: idle agents only. An agent in the middle of a turn is left alone.
- Where to: the account with the most room that is signed in on the same machine.
- What it never moves: an agent pinned with "Keep on this account". You can still move a pinned agent by hand.
- How often: at most once every 30 minutes for each agent.
- The record: Recent moves lists each move with the time, both accounts and who moved it.
Each account must be one you pay for and use yourself. See what Anthropic's terms say about more than one Claude account.
Get an alert before every account runs out
Auto-move needs somewhere to put an agent. When every account is low, Orpheus tells you instead, by email, by a notification on your devices, or both.
- First alert: every account is at 85% of its week or more, or on track to run out before it resets.
- Second alert: every account is at 95% of its week or more.
Each alert is sent once a week. Email alerts are on by default for owners and admins, and each member can change their own. Browser notifications work in Chrome, Edge, Firefox and Safari on a computer, and on Android. On iPhone, add Orpheus to the Home Screen first. You can also get a notification each time Auto-move moves an agent.
Common questions
Does Orpheus sell Claude subscriptions?
No. You connect the Claude subscriptions you already pay for. Orpheus reads their usage and moves agents between them.
Will Auto-move interrupt an agent in the middle of a task?
No. It only moves idle agents. An agent in the middle of a turn stays where it is until it goes idle, and a pinned agent is never moved.
Does a moved agent lose its conversation?
No. Orpheus restarts the idle session in the same tmux pane and folder under the other account with claude --continue, so the conversation carries on.
When do I get an alert?
When every account is at 85% of its week or more, or on track to run out before it resets, and again when every account is at 95%. Each alert is sent once a week, by email, to your devices, or both.
Which plan do I need?
Usage, reset times and forecasts are on every plan, from Solo at $19 a month for 1 account. Moving agents and Auto-move need a second account, so they start on the 2 accounts plan at $29 a month.
Sources
- How do I check my Claude Code usage?Orpheus guidesChecked
- Managing multiple accountsOrpheus docsChecked
- Setup guideOrpheus docsChecked
- PricingOrpheusChecked