notis handover gives that branch to a Notis agent. It picks the work up on your
cloud computer, in its own git worktree, and keeps going.
Who runs it
Every hand-over says who runs it and how, so the work starts exactly the way you asked.--route names the agent:
Naming an agent works like saying it in a message: it wins for this task. Codex and Claude run
on your own subscription rather than on Notis credits, and keep going when you close the laptop.
How much thinking, and how fast
--intelligence sets how much reasoning the agent uses: low, medium or high, the same
intelligence levels as in
the app, or auto to let Notis choose. --speed sets how fast it runs, with the same speeds as
in the app:
Codex and Claude only run Fast when their own fast mode is available on your account. See
processing tiers for
what each speed costs.
Ask the coding agent in your terminal to hand the work over and it chooses all three from what
you say: “get Claude on it, this one is tricky” becomes
--route claude --intelligence high --speed normal. Use auto only when you want Notis to choose.
Your branch, or a new one
By default the agent cuts a new branch from yours and works there, so you can carry on where you are without two people committing to one branch.--branch-mode same when you are handing the branch over and stepping off it. The
agent commits straight onto it, so pull its work down with git pull --rebase before you
touch that branch again, and do not force-push it.
Getting the work back
The agent opens a draft pull request early, so the work is visible without you watching it. Each hand-over is also a conversation in your Notis app, whichever agent runs it, so you can follow it and ask it questions there like any other task.handover start ends by printing the handover status command for that hand-over. Run it to
see how the work is going and read the result. With no id, handover status lists the work
Notis is still running for you.
If the command cannot tell whether the work started, it prints the exact next step: usually
checking handover status first, and handing over again only if nothing started. Follow it
rather than starting over, so the work never runs twice.
What it does with uncommitted work
The cloud workspace is built from your remote, so anything you have not pushed would simply not be there. Rather than silently leaving it behind, the hand-over commits it for you as awip: commit and pushes it.
That commit takes everything git can see, including untracked files that are not
in your .gitignore. The hand-over refuses common secret files and private keys, but
you should still check git status first. Pass --no-wip to make the command refuse
on any uncommitted work instead and commit it yourself.
Requirements
Sign in once withnotis login. Your repository has to be reachable: a branch, an origin remote, and push access. The
first hand-over for a repository Notis has not seen before takes longer, because the agent
configures it on the cloud computer first.
Hand-over only goes one way: from your machine to Notis. An agent that Notis is already
running cannot hand its own work back, which is what stops two agents passing the same task
between them forever.
Related
- Agent routing overview: how Notis picks the agent.
- Connect your agents: sign Codex and Claude in.
- Cloud Computer: where Codex and Claude do the work.

