A worktree for every session
Each coding agent task gets its own Git branch and worktree instead of editing the same checkout as every other task.
Give every coding agent task an isolated workspace.
Separate more than the branch. Neroli keeps each agent's worktree, terminals, services, provider context, tools, and changes attached to one task from setup through review.
Neroli is currently in beta on macOS.
- A dedicated branch and worktree per session
- Repository-owned setup and run commands
- Tools and changes attached to the task
Why Neroli
Isolation that includes the working environment.
Parallel coding agents need independent checkouts, but they also need clear process, port, tool, and review boundaries.
An environment around the code
Keep terminals, panes, environment setup, running services, provider state, and artifacts attached to the isolated session.
Ports and setup you can repeat
Repository-owned Workspace Commands can copy allowed setup, allocate ports, install dependencies, and start or stop services.
Several tasks, one clear overview
See which workspace is active, waiting, failed, or ready for review without reconstructing state from terminal tabs.
The provider context stays attached
Return to the direct agent conversation, terminal output, and task tools in the same workspace where the code changed.
A deliberate path to merge
Inspect the session's changes and run its environment before merging the branch or archiving work you do not want.
The workflow
Create, prepare, run, review.
Neroli gives each task a repeatable workspace lifecycle while the repository remains the source of truth for project-specific setup.
- 1
Choose the repository and base branch
Start with the exact codebase and branch the task should build on. Neroli creates the session branch and separate Git worktree.
- 2
Prepare the session environment
Run repository-owned Workspace Commands to apply the setup the project needs, including allowed files, dependencies, ports, and services.
- 3
Let the agent work inside the boundary
The provider conversation, edits, terminals, dev servers, browser, and other panes remain associated with that one task.
- 4
Validate, merge, or archive
Review the diff and exercise the isolated environment. Merge trusted work through your normal Git workflow and close the completed session.
Git isolation
A branch is useful. A whole workspace is safer to reason about.
A Git branch separates commits, but simultaneous coding work also has terminal state, generated files, processes, and ports. Neroli makes the session the operational boundary.
- Dedicated branch and Git worktree
- Changes scoped to the correct session
- Review before work reaches the base branch
Environment
Repeat the repository's own setup.
Workspace Commands are project-owned shell workflows. They make session setup explicit instead of hiding it in a developer's terminal history.
- Prepare allowed environment files
- Assign ports for concurrent services
- Start, check, and stop repository tools
Continuity
Open the task and recover its context.
The code is only one part of agent state. Neroli restores the task's panes and provider conversation so you can understand what happened and what needs attention.
- Provider conversation in the session
- Attached terminals and product surfaces
- Visible task and review state
Questions
What developers ask.
What is an isolated coding agent workspace?
It is a task-specific working area with its own Git branch and worktree, provider session, panes, commands, services, and changes. The boundary keeps parallel tasks understandable and reduces accidental overlap in one checkout.
Why use Git worktrees for coding agents?
Git worktrees let separate branches exist as separate directories at the same time. That gives each coding agent a real checkout where it can edit and run code without switching the directory another session is using.
Does a worktree isolate development servers and ports?
Not by itself. Neroli Workspace Commands can prepare session-specific setup and ports, but the repository must define the commands appropriate for its own services and environment.
Can Claude Code and Codex use the same repository at once?
Yes. They can run in separate Neroli sessions, each with its own branch and worktree. Any shared external service still needs project-appropriate isolation or coordination.
Can I review changes before merging?
Yes. The session keeps the branch, diff, command output, and validation surfaces together so you can inspect and run the work before deciding what lands.
Field guide
Apply the workspace model to a real Xcode app.
See how to isolate builds, app identities, local services, verification evidence, and cleanup across task-owned worktrees.
Read the Xcode software factory guideNeroli 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