Run coding agents in parallel without losing the work.

Give every task its own worktree, agent session, terminals, tools, and review path. Neroli keeps the fleet visible from one fast native Mac workspace.

Request access Read the docs

Neroli is currently in beta on macOS.

Why Neroli

The workspace around the agents matters.

Running three agent processes is easy. Keeping their branches, services, approvals, evidence, and results understandable is the actual orchestration problem.

One worktree per session

Each task gets its own branch and Git worktree, so agents can edit, install dependencies, and run checks without sharing one checkout.

Keep the real agent interface

Run Claude Code, Codex, or another supported provider through its direct terminal interface instead of a reduced chat wrapper.

See what needs you

Session state tells you which agent is planning, running, waiting for approval, ready for review, failed, local, or in cloud.

Attach the working environment

Terminals, dev servers, browsers, simulators, diffs, and artifacts stay with the session that created them.

Repeat the setup

Workspace Commands can prepare environment files, allocate ports, start services, run builds, and stop what the session no longer needs.

Run locally or in cloud

Keep interactive work on your Mac, start a task in cloud, or move a supported long-running session when it should continue elsewhere.

The workflow

Dispatch, supervise, verify, merge.

Neroli turns parallel agent work into a queue you can operate instead of a collection of terminals you have to remember.

  1. 1

    Choose a repository and a bounded task

    Create a Neroli session for work that can move independently: a feature, fix, test pass, documentation update, or experiment.

  2. 2

    Dispatch the right coding agent

    Start Claude Code, Codex, or another configured provider. Neroli prepares the isolated worktree and restores the workspace panes for that task.

  3. 3

    Work the ready queue

    Start more sessions while the first agent runs. Return when an agent needs approval, has failed, or has produced work ready to inspect.

  4. 4

    Run the result before it lands

    Use the session's tests, browser, simulator, and diff to verify the behavior. Merge the work you trust and archive the rest.

Isolation

Parallel work without a shared checkout.

Git branches alone do not protect running services, generated files, or an agent's conversation. Neroli makes the entire session the unit of work.

  • Dedicated branch and worktree
  • Session-specific panes and terminal state
  • Repository-owned setup and run automations

Attention

Supervise by state, not by tab count.

A fleet is useful only when you can tell what is moving and what is blocked. Neroli keeps the work visible without flattening every provider into the same UI.

  • Clear running, approval, review, and failure states
  • Direct access to the provider conversation
  • Diffs and tools attached to the correct session

Proof

Make validation part of the handoff.

A finished agent response is not the same thing as finished software. The session keeps the surfaces needed to exercise what changed.

  • Repository checks and builds
  • Real browser and simulator interaction
  • A review path before merge

Questions

What developers ask.

What is coding agent orchestration?

For Neroli, orchestration means creating isolated sessions, starting the chosen coding agent, keeping its tools and state attached, showing when it needs attention, and giving the result a consistent review path. It does not require replacing the underlying agent.

How does Neroli keep parallel agents from overwriting each other?

Each session uses its own Git branch and worktree. Workspace Commands can also give sessions distinct ports and setup so their running development environments do not have to collide.

Which coding agents can I use?

Neroli is designed around provider choice and directly supports Claude Code and Codex workflows. The product documentation carries the current provider details as beta support expands.

Do all sessions have to run in the cloud?

No. Neroli is local-first. Sessions can remain on your Mac, start in Neroli Cloud, or move to cloud when a supported task should keep running elsewhere.

Can I review an agent's changes before merging?

Yes. The session keeps its branch, changes, terminals, and validation tools together so you can inspect and run the result before deciding what lands.

Field guide

Take parallel Xcode work all the way to merge.

Follow one task from an isolated worktree through the exact app build, review evidence, pull request, and cleanup.

Read the Xcode software factory guide

Keep exploring

Isolated workspaces Give each parallel task its own branch, worktree, tools, and services.
Coding agent automations Turn repeatable agent and repository work into visible runs.
Cloud coding agents Let long-running sessions continue away from your Mac.

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