Placeholder image: a Neroli workspace with several isolated sessions, direct TUI panes, Run and Build actions, and a Cloud handoff status.
Neroli turns one-agent-at-a-time coding into a fast parallel workspace.
Why Neroli exists
Coding agents are powerful enough to run more than one thread of work at a time. The hard part is everything around them: isolation, visibility, setup, review, handoff, and knowing which session needs you. Neroli gives that work a home. Each agent gets a real workspace, direct provider TUI, panes, automations, status, review, and optional cloud handoff. It is built around a few ideas:- Provider freedom: use the agents you already like, alone or side by side.
- Sessions: each agent run gets its own branch, worktree, panes, and state.
- Direct TUIs: Neroli runs the real provider interfaces instead of wrapping a stale subset.
- Automations: your workspace can set itself up, run, build, verify, stop, and improve.
- Cloud handoff: snapshot a session and keep it running elsewhere, then bring it back.
What this unlocks
Build in parallel
Run a feature, a test pass, a docs update, and an experiment without mixing files.
Keep context visible
Terminals, browser panes, simulators, diffs, artifacts, approvals, and status stay attached to the session.
Let agents use the workspace
Agents can inspect sessions, use attached browsers, run automations, and create better automations for next time.
Move without lock-in
Snapshot a local session into cloud, keep it running, then bring the result back to the same workspace.
The flow
1
Launch fast
Open Neroli, choose a repo, and start a new session without fighting project setup or terminal sprawl.
2
Run agents in parallel
Dispatch multiple agents into isolated sessions so features, fixes, experiments, tests, and docs can move at the same time.
3
Watch what needs you
Neroli shows what is running, waiting for approval, blocked, failed, ready, local, or cloud.
4
Let the workspace run itself
Automations can copy env files, assign ports, start dev servers, run checks, stop services, and even suggest better automations.
5
Move work when needed
Handoff snapshots the session conversation, edits, and workspace state into cloud, then brings work back local when you want it.
Read this way
Start
Open the app, connect your agents, and launch your first session.
Concepts
Understand workspaces, sessions, worktrees, panes, and status.
Session board
Manage parallel sessions like a lightweight issue tracker.
Automations
Teach the workspace how to set up, run, build, stop, and improve itself.
Cloud
Snapshot sessions into cloud, run more agents, and bring work back local.
Review
See what changed and choose what lands.
Recipes and gotchas
Set up isolated dev sessions, cloud handoff, self-review, and common fixes.
What matters
- Speed: the app boots fast and gets you into a session quickly.
- Provider choice: Neroli is the layer on top, not the agent you must adopt.
- Feature parity: direct TUIs mean provider features work as soon as providers ship them.
- Isolation: sessions can experiment without colliding.
- Visibility: terminals, browsers, simulators, diffs, and artifacts stay attached to the session.
- Automation: scripts and agentic sessions can keep improving the workspace.
- Portability: work belongs to the workspace, not a single provider or runtime.
Neroli is local-first by default. Cloud is there when a session should keep running somewhere else.