claudeClaude Code
Keep your work plan and your personal one open at the same time.
Every account you own, running at once.
Run Claude Code, Codex and Antigravity side by side, each signed in as a different account, in one window.
workclaudeclientcodexossagyand the rest
three agents, three accounts, one window
Signing in twice signs you out once.
Every one of these tools allows a single account on a machine. Adding a second one takes the first away. Nuvoa runs up to sixteen at the same time, each signed in on its own, in one window.
codexCodex
Keep a client's account away from everything else.
agyAntigravity
Add as many accounts as you have, and put every one of them to work.
Every pane is its own workspace.
Opening a pane gives that account somewhere to work that belongs to it alone. Nothing it does reaches anything else you have open.
Its own account
Sessions never sign each other out, and none of them can see another's history or settings.
Its own copy of the code
Two agents can work on one project at the same time without overwriting each other. Each keeps its work on a branch of its own.
Your setup, unchanged
Your commits are still yours, and the tools an agent reaches for behave exactly as they do in your own terminal.
one pane, one account, one folder
Crown one pane. It commands the rest.
- You type one goal into the bar at the top and hand it to whichever pane you put in charge.
- That pane reads the project and turns the goal into a task for every other account you have open.
- The tasks run at the same time, each one somewhere of its own. An account that is out of quota waits, then starts itself.
- Everything comes back together on a single branch, for you to read before any of it is yours.
every account, and what it has left
Ask what is left before you spend it.
Every account can say how much of its window it has left, and when that window comes back. Asking costs nothing and never interrupts a session that is already running.
Plan a round before you start it
See which accounts can take real work and which are nearly spent, rather than finding out halfway through.
A limited account is not a lost one
Its work is held and picked up the moment the account is usable again, hours later if that is what it takes.
A guess never looks like a fact
When a reset time has to be estimated, it is shown as an estimate.
You give it a goal. It runs the room.
The pane you crown keeps going in rounds until the goal is met or it runs out of ways to make progress. Waiting out a usage limit counts as waiting, not as failing.
Hand out the work
- One task per account
- The goal is split so no two agents are working on the same files.
- Matched to the job
- Each task gets the model and the amount of thinking it actually needs.
- Nothing sits idle
- Every account with a pane open is part of the fleet. There is no second list to keep up to date.
Watch it happen
- Live in every pane
- Output streams as it arrives, so you can tell working from stuck at a glance.
- Quota in the sidebar
- How much each account has left, next to its name.
- Talk to it mid-run
- Ask the pane in charge what it is doing, or tell it to try something else.
Get it back
- Out of quota is not out
- Work for a limited account waits, then starts itself when that account comes back.
- One branch at the end
- Every agent's work is brought together for you to look at.
- You do the merging
- Your own copy is never touched, and nothing is ever pushed.
What this costs you.
An agent working on its own cannot stop to ask your permission, so it does not. Each one is kept to its own workspace, but it is running real commands on your machine while you are not watching. That is the trade, and it should be a deliberate one.
macOS only
There is no Windows or Linux build, and there is not going to be a quick one.
You still review the work
What comes back is a branch, not a merge. Nothing lands in your project until you put it there.
One task per account at a time
An account that is already busy waits its turn rather than doubling up.
Codex panes are quiet while they work
Two of the three stream their output live. Codex shows its result when it finishes.
The pane in charge spends quota too
Planning runs on one of your accounts. If that one runs dry the run pauses, and picks up where it left off.
Splitting the work is a judgement call
The pane in charge divides the job so agents stay out of each other's way. It is usually right, and it is not guaranteed.
None of this is taken on trust.
The promises on this page ship with checks that prove them, and those checks run on your own machine without a network or a model. If a claim here stops being true, they fail.
checks that ship with the app
- Two accounts really are separate, and neither one can reach the other's sign-in.
- Work from every agent arrives on the merged branch, including anything one of them forgot to save.
- A genuine conflict is reported as a conflict, never quietly half applied.
The questions people actually ask.
Answered the same way here, in the docs and in the file the models read, so you get one answer rather than three.
Can you run two Claude Code accounts on one Mac?
Not with the CLI on its own. Claude Code keeps one signed-in account per machine, so signing into a second one signs the first out. Nuvoa gives each account its own pane with its own credentials, so up to sixteen stay signed in at once and none of them can read another's session.
Does Nuvoa work with Codex and Antigravity too?
Yes. Claude Code, Codex and Antigravity all run as panes in the same window, and every pane is signed in as an account of its own. You can mix them however you like, including several accounts of the same tool.
What happens when an account hits its usage limit?
The work that account was given is held rather than dropped. Nuvoa waits for the usage window to come back, hours later if that is what it takes, then starts the task itself. The sidebar shows how much every account has left before you commit to a round.
Do the agents overwrite each other's work?
No. Each pane gets its own copy of the code on a branch of its own, so two agents can work on one project at the same time. Everything is brought back together on a single branch for you to read.
Does Nuvoa push to my repository?
Never. What comes back is a branch, not a merge. Your own copy is untouched and nothing is pushed anywhere until you do it.
Is Nuvoa available on Windows or Linux?
No. Nuvoa is macOS only and there is no quick path to a Windows or Linux build.
Is Nuvoa an API wrapper, and does it cost extra tokens?
It is neither. Nuvoa drives the official CLIs you already have installed, signed in with the subscriptions you already pay for. There is no API key to add and no second bill for tokens.
How much does Nuvoa cost?
Nuvoa is in private testing on macOS and pricing is not set. Creating an account gets you one email when there is a build to try, and the download page when there is.
Written down, so you can check.
All writingBuilt for people already running three of these.
Nuvoa is in private testing on macOS. Your account is your address and nothing else: no password to pick and none for us to lose.