Move the session, not a copy
Handoff moves the running session itself: the branch and worktree edits, the provider conversation and its resume state, and the pane layout around them. You continue one thread instead of reconciling two.
Cloud coding agents that return to your Mac.
Execution location is a property of the session, not a decision you make once. Send a running session to Neroli Cloud when you step away, then bring it back with its branch, conversation, and panes to review and run the result on your Mac.
- Local-first by default
- Isolated cloud environments
- The session makes the round trip
Why Neroli
Cloud should extend the workspace, not replace it.
A one-way trip to the cloud leaves you merging a copy back by hand. Neroli moves the session in both directions, so the Mac stays the place you supervise, inspect, and finish the work.
Bring the whole thing home
The return trip carries the same material back to your Mac. There is no one-way mirror to merge by hand and no local edits to overwrite.
Stay local by default
A local session uses the repository, tools, credentials, and processes on your Mac. Nothing leaves it until you choose cloud execution for that session.
Run in an isolated environment
Each cloud session gets its own runtime: repository setup, selected tools, network policy, and the cloud credentials you connected for it.
Keep status in the Mac workspace
Starting, running, waiting, ready, or recovering — cloud sessions report to the same session board as local work, so one place still shows everything.
Nothing moves by accident
Git-ignored files, local browser profiles, and the provider login stored on your Mac stay where they are. Handoff carries work, not your whole machine.
The workflow
Move the session, keep the thread.
Handoff is explicit in both directions: configure the environment, choose when the session moves, watch its state, and bring it back for local verification.
- 1
Configure the cloud environment
Choose the repository setup, allowed network access, environment variables, and a provider credential intended for cloud use.
- 2
Send the session up
Hand off a running local session with its conversation, repository changes, and workspace state, or start the work in cloud directly.
- 3
Let it run without you
The cloud environment keeps going when your Mac sleeps or closes. Neroli reports the session state and tells you when it needs attention.
- 4
Bring it back and verify
Return the session to your Mac, restore its panes, inspect the diff, and run the local validation path before anything merges.
What moves
Enough state to continue the same session.
Handoff snapshots the provider state and the workspace material needed to pick the thread back up, in both directions.
- Repository changes and allowed untracked files
- Provider conversation and resume state
- Pane layout and workspace state
What stays local
Private local state does not move by accident.
Cloud is a distinct environment. Local browser profiles, git-ignored files, and the provider login stored on your Mac are not silently copied into it.
- Local browser profiles
- Git-ignored files
- Local provider login credentials
Cloud boundary
Connect cloud access deliberately.
Cloud environments use separately connected credentials and explicit setup. Secret values are encrypted at rest and masked when returned to the app.
- Separate provider credential for cloud use
- Explicit environment and network policy
- Isolated cloud browser state
Questions
What developers ask.
Can I bring a cloud session back to my Mac?
Yes, and this is the point of the design. Handoff returns the provider conversation, repository changes, and workspace state to the local session, so you continue the same thread on your Mac rather than merging a copy by hand.
Is Neroli Cloud a separate mode from local work?
No. Execution location is a property of a session, not a choice you make once when you create it. The same session can start on your Mac, run in cloud while you are away, and come back to be finished locally.
Will a cloud coding agent keep running after I close my Mac?
Yes. A session running in Neroli Cloud executes away from your Mac, so long-running work continues while the Mac is asleep or closed.
Does Neroli upload every local repository?
No. Neroli is local-first. A local worktree is uploaded only when you explicitly move that session to cloud. A session created directly in cloud starts from its configured repository and branch.
Does my local Claude Code or Codex login move to cloud?
No. Cloud sessions use a separate provider subscription login or API key that you connect for cloud use. The provider receives agent requests directly from the cloud session.
What does not move with a cloud handoff?
Git-ignored files and local browser profiles do not move. Cloud browser state is separate and stays inside the cloud environment where it was created.
Neroli beta
One Mac workspace for all your coding agents.
Tell us how you work today and which provider you want to run first.
Request access