Orpheus
Start 14-day trial
Multiple Claude accounts

Run all your Claude subscriptions from one place.

Orpheus puts every Claude account you pay for on one board: how much of the weekly and 5-hour limit is used, what each is on track for, and when it resets. When one is about to run out, Orpheus moves idle agents to the account with the most room. On the web and on your phone.

Start 14-day trialSee plans for 1 to 12 accounts
$0 today. 14-day trial on every plan, from $19 a month for 1 Claude account. Card required.
Your own subscriptionsOrpheus does not resell Claude. Your agents keep using the accounts you pay for.
Outbound onlyThe connector dials out to Orpheus. You open no ports.
Open-source connectorMIT licensed. Read every line your agent installs.
Your policy, your machineA local file decides what is shown. We cannot change it.
Several accounts, one board

Stop finding out an account is empty when an agent stalls.

With more than one Claude subscription, the limits are spread over logins and machines. Orpheus reads them all and acts before one runs out.

Every limit, per account

For each account: percent of the weekly limit and of the 5-hour limit used, what it is on track for by reset, and the reset time.

Week86%On track for 118% by reset.
5 hour41%Resets 4:10 PM.

Auto-move before an account runs out

Set a threshold per account. When it is reached, Orpheus moves idle agents onto the account with the most room. An agent in the middle of a turn is left alone until it goes idle.

pr-review work → personalAutowork reached 92% of its 5-hour limit.

Or move a session yourself

Every session has a Move to action. It lists your other accounts with the room each has left, so you pick with the numbers in front of you.

personalMost roomWeek 22%, on track for 41%. 5 hour 12%.
Also in Orpheus

And every agent on those accounts, in one window.

Live panes

Open any agent as a clean chat view or as its live terminal, side by side, from every machine. A session waiting on you is marked.

flaky-testsneeds you
billing-webhooksCLAUDE

Broadcast

Send one instruction to one agent or to several at once. Handy for "commit and push" at the end of the day.

refactor-authbilling-webhooksmigrate-dbdocs-site

Asks

An agent that needs a decision asks you. Answer from your phone and the answer is typed back into its session.

migrate-db asksApply migration 003 to staging now?
ApplyWait

Decision Matrix

What each agent is waiting on, with a recommendation, on one page. Answer yes, no or discuss.

Merge the auth refactor?YESNO

Rooms

Put a few agents in one room to work on the same problem, and read the thread as it goes.

Setup

Connect your Claude accounts by pasting one prompt.

You don't install anything by hand. The agent already on that machine does it.

  1. Copy the prompt

    Orpheus gives you a prompt with a one-time token inside. The token lasts 15 minutes and works once.

  2. Paste it to an agent on your machine

    The agent installs the open-source connector. It connects the machine and finds the Claude logins on it.

  3. Your accounts appear on the board

    Name them, choose which sessions to share, and get the phone app. Repeat on each machine you run agents on.

Read the setup guideHow the connection works
Fits what you run

It doesn't wrap Claude. It works beside it.

Orpheus does not replace Claude Code and does not sit between you and it. Your agents keep running in tmux on your own machines, on your own subscriptions.

The connector reads the limits, shows the sessions, and switches which signed-in account a session uses when you or auto-move ask. Remove it and every agent carries on.

Security

Built so that we can't reach into your machine.

The connector is small, open source and limited on purpose. Here is the whole list.

The connector can
  • List the tmux sessions your policy exposes and stream their output
  • Type text and a short list of keys into those sessions
  • Read usage for the Claude accounts signed in on that machine, and switch a session between them
It cannot
  • Run an arbitrary command. The protocol has no message for it.
  • Accept an inbound connection. It only dials out.
  • Have its policy changed from our side. The file is edited on your machine only.
Read the security page
Pricing in beta

Pick the plan by how many Claude accounts you run.

Solo$19 / mo1 Claude account 2 accounts$29 / moAuto-move starts here 4 accounts$49 / mo$12.25 an account 8 accounts$89 / mo$11.13 an account 12 accounts$119 / mo$9.92 an account

Every plan starts with a 14-day trial. The trial needs a card: $0 due today, and you are charged when the 14 days end unless you cancel. Pay yearly and a year costs 10 months.

Start 14-day trialFull pricing
Questions

Asked before signing up

Does Orpheus include a Claude subscription?

No. You connect the Claude subscriptions you already pay for, and your agents keep using them. Orpheus shows their limits and moves agents between them.

What does auto-move do?

When an account gets close to its weekly or 5-hour limit, Orpheus moves idle agents off it and onto the connected account with the most room. You set the threshold per account and can turn it off.

Can Orpheus run commands on my machine?

No. The connector types into tmux sessions that your policy exposes, and sends a short list of keys. There is no message in the protocol that runs a command.

Does it work with the agents I already have running?

Yes, if they run inside tmux. The connector finds Claude Code sessions on its own. Nothing about how you start or use them changes.

What happens if I close Orpheus?

Nothing happens to your agents. They run on your machines, on the account they were last on.

All questions

Connect your Claude accounts.

Pick the plan that matches your accounts. 14-day trial, $0 today.

Start 14-day trialSee plans