The personal hub for your agent accounts and machines.
Pool your Claude and Codex subscriptions, share them with every machine you own, and send work to whichever machine has room. It works under whatever runs your agents now.
Free and open source, for Macs with Apple silicon. How it works




Sample accounts and machines. It all runs in your browser, so nothing you do here goes anywhere.
One proxy between your machines and your accounts
Agents send their requests to Arbor's proxy, which passes each one to an account with room left.
- studioClaude Code in a desktop app
- labCodex over SSH
- miniClaude Code in a terminal
- Add machine
- claude-maxClaude · Max 20x · 78% left
- claude-workClaude · Max 20x · 42% left
- codex-teamCodex · Pro · 14% left
- Add account
Add an account
Every machine can use it straight away.
Add a machine
It gets every account you've signed in.
An account hits its limit
Requests go to the others until it resets.
A machine is busy
The next run goes to another in its pool.
Works with the agent app you already use
Claude Code and Codex pick up the proxy from their own settings, so whatever starts them uses your accounts. When Arbor starts a run, it hands it to the app on that machine.
Your terminal or agent app
- Runs the sessions
- Worktrees, branches and diffs
- Chat, approvals and pull requests
Arbor
- Signs each account in once and shares it with every machine
- Moves to the next account when one hits its limit
- Sends each run to a machine with room
- Checks each machine's health and agent versions
- Keeps skills, instructions, MCP servers and plugins the same
- Records usage and spend across every machine
Stop switching accounts
Sign each Claude and Codex account in once. Arbor tracks every limit and spreads the work across them.
- ClaudeFor Claude Code
- ChatGPTFor Codex
- xAIFor Grok models
Every limit in one place
Each account's limits, added up per provider.
- The 5-hour, weekly and per-model windows, and when each resets
- A warning when you'll run out before the reset
- Claude's banked resets and Codex's reset credits

In the order the proxy uses them
Accounts are listed in the order the proxy tries them, with a reason beside any it's skipping.
- Pause an account at any cap you set; the cap eases as the reset nears
- Suggests an order that uses up the accounts resetting soonest

What each subscription is worth
Every request is priced at API rates and added up per account.
- Value against what each subscription costs
- Which subscription you could drop
- Spend per session, project and week

Across all your machines
Point your Macs and Linux machines at the proxy and they share the same accounts.
A page for every machine
Arbor checks each machine over SSH and shows what its agents are running.
- CPU, memory, disk, network and latency
- Which Claude Code and Codex it runs, with an update when one's behind
- Start an agent to fix a warning, from the warning itself

Every session, whatever started it
One live list of Claude Code and Codex sessions on all your machines, grouped by machine and project.
- Waiting on you, working, failed or done
- An alert on your Mac or phone when one needs you

The same setup everywhere
Instructions, skills, MCP servers, plugins and hooks compared across machines and coding agents, and kept in step from a git repo.
- Finds broken links, clashing skills and drift
- Shows every change before it's made
- Backs up first, and every change can be undone

Send work where there's room
Group machines into pools. Each run goes to a machine with room, on accounts with room.
Pick the machine with room
Arbor weighs each machine's agents, CPU and memory, and shows where the next run would go.
- Prefer a machine, use one less often, or keep one for runs you start yourself
- When a pool is full, wait, spill into another pool or turn the run away
- A run is handed to the agent app or command line on the machine Arbor picks

Every scheduled run in one list
Arbor's own automations, and the ones your other apps scheduled, from every machine.
- Run on one machine, or on whichever pool member has room
- Ones set to run on their machine keep going with Arbor closed
- Claude and Codex runs use your accounts through the proxy

One SSH host per pool
Connect to a pool like any other host, from a terminal or any app that uses SSH.
- Host keys come only from your own known_hosts
- One line added to ~/.ssh/config, backed up first
$ ssh arbor-builds # lands on mini, the member with room $ ssh arbor-builds # mini again: a host name stays on its machine
Your agents can use Arbor too
The arbor command lets you, or any agent on your Mac, read limits, machines and usage, and make the changes you agree to. Each change shows in the window straight away.
- An MCP server and an agent skill, installed from Settings › App
- Anything Arbor would confirm prints a plan and waits for --yes
- Account tokens and other secrets are never shown
$ arbor status # proxy, machines, live sessions, accounts running low $ arbor accounts # every account's limits and when they reset $ arbor usage 7d # requests, tokens and cost for the week $ arbor pools # which machine would take each pool's next run $ arbor sync apply mini # prints the plan; runs only with --yes
Also in Arbor

Alerts
Your Mac or phone tells you when an agent is waiting, a machine drops out or a limit runs ahead.

Weekly report
Spend, merged pull requests and the costliest sessions, exported as one page.

Projects
Sessions grouped by project, with the pull requests they opened and what each cost.

Agent updates
Try a new Claude Code or Codex on one machine, compare its failures, then update the rest.

Every request
Each one's machine, client, model and tokens, and why any failed.

Session archive
Every transcript from every machine, copied to a drive you choose.

All-time tokens
Every token back to your first session, by model, machine and month.

Search
⌘K opens any page, project, session, machine or account.

Updates
Stable releases, or nightly builds of what's next. The proxy keeps serving through an update.
Privacy
Sign-ins stay on your Mac
Only the Mac that runs Arbor holds your accounts. Other machines get the proxy's address and a key.
Counts, not conversations
Arbor reads session ids, times, models and token counts, never prompts or replies. Only the session archive copies whole transcripts, to a drive you choose.
Usage data you can turn off
Anonymous usage data and crash reports help fix Arbor. Turn them off in Settings › App.
Questions
Can I download it?
Yes, for Macs with Apple silicon, from the latest release on GitHub. It isn't notarized yet, so the first time it opens, choose Open Anyway in System Settings › Privacy & Security. Updates install themselves after that.
Is it open source?
Yes, MIT licensed. The source is on GitHub, and every release is built from it.
Does it change how my agents work?
Only where they send their requests. Claude Code and Codex read the proxy's address from their own settings. Nothing else on a machine changes unless you bring its setup in step from Sync.
Which accounts can it use?
Claude and ChatGPT accounts for Claude Code and Codex, signed in through each provider's own sign-in page. xAI works too.
Which coding agents does it work with?
Claude Code and Codex use your pooled accounts. Sync also keeps instructions, skills and MCP servers in step for other coding agents on your machines.
What does another machine need?
Its Claude Code or Codex pointed at the proxy. For health checks, pools and keeping its setup in step, SSH access from the Mac that runs Arbor.
Does it run on Linux?
Arbor itself runs on a Mac. The machines that share its accounts can be Macs or Linux.
Does Arbor have to stay open?
Agents send their requests through the proxy on the Mac that runs Arbor, so keep it running there. Automations set to run on their own machine run with Arbor closed.
Is it for teams?
No. It's for your own accounts on your own machines.
What's new
- 1.0.18Arbor from the command lineThe arbor command and an MCP server, so you and your agents can check limits, machines and usage, and make changes you agree to.
- 1.0.11Every machine at a glanceThe sidebar shows each machine's health and working agents, and each provider's limits, with details on hover.
- 1.0.8Edit your setup repo in ArborBrowse the setup repo's files, see which machines have the latest of each, then edit and commit them together.
- 1.0.0Arbor 1.0Choose stable releases, or nightly builds of what's next.