Skip to main content
These are the workflows that make Neroli feel different from scattered terminal tabs. Start with the one that removes the most friction from your current repo.

​
Isolated dev sessions

Use this when parallel agents need to run the app, database, or test stack at the same time.
1

Prepare the session

Copy .env.local or generated config into the session without committing secrets.
2

Assign unique ports

Give each session its own frontend, backend, database, queue, or simulator ports.
3

Isolate services

Use a unique Docker project name, database name, schema, cache prefix, or local data directory for each session.
4

Expose Run and Stop

Pin Run in the toolbar and add Stop behavior so the session can clean up after itself.
5

Add Verify

Give humans and agents one command that proves the session is ready for review.

​
Parallel feature work

Use this when you want several directions explored without mixing files.
  1. Start one session per feature, fix, experiment, docs update, or review.
  2. Give each session the context and outcome it needs.
  3. Move planning work into Planning and active work into In Progress.
  4. Let sessions run in parallel while Neroli tracks which ones need input.
  5. Move substantial candidates to In Review and ask each agent to self-review.
  6. Put validated candidates in Merge, then move them to Done or archive them.
The point is not to make every task tiny. The point is to keep each stream of work inspectable.

​
Group automation

Use this when a sidebar group keeps collecting the same manual work.
1

Pick the group

Choose the group where the work naturally gathers: In Review, Merge, Done, or another stage.
2

Create the action

Add a sidebar automation for that group. It can inspect the sessions in the group and act on the first or all of them.
3

Run from the header

Launch the automation from the group header instead of opening each session by hand.
4

Use moved triggers when useful

If entering a group should start follow-up work, use a Session moved automation for that destination.

​
Browser verification

Use this when an agent changes a visible web flow.
1

Start the app from the session

Use the session’s Run automation so the browser points at the right worktree.
2

Open the attached browser

Keep the page in a Neroli pane so the agent and human are looking at the same UI.
3

Ask the agent to verify

Have it inspect the page, click through the changed flow, check console or network evidence when useful, and report what it saw.
4

Review the evidence

Use the browser state, screenshots, logs, and diff together before merging.

​
Cloud handoff

Use this when a session should keep running away from your Mac, or when you want more agents moving at once.
1

Start local

Get the session into a useful state locally first. The handoff snapshot includes conversation context, file edits, and workspace state.
2

Check setup

Make sure the workspace knows how to install, build, run, and verify itself without hidden local state.
3

Move to cloud

Send the session to cloud and keep watching status in Neroli.
4

Bring it back

Move the result local, run verification from the session, and review before merging.
Cloud is not a place to hide messy setup. If setup, secrets, or network access are unclear locally, fix that before relying on handoff.

​
Agent self-review

Use this before you read the diff yourself.
Good self-review includes the changed behavior, verification result, known risks, and any files you should inspect manually.

​
Keep artifacts reviewable

Use this when agents generate docs, images, PDFs, spreadsheets, notebooks, or other output files.
  • keep source-code edits in Changes
  • keep generated outputs visible as artifacts
  • ask the agent which artifacts are final and which are scratch
  • open important artifacts in a file viewer before merging
  • ignore bulky build outputs unless they are intentional deliverables

​
Gotchas

​
When to add an automation

Add one when you repeat a task more than twice, when agents keep asking how to run something, or when a setup mistake blocks parallel work. Good automation names are clear and obvious: Prepare session, Run dev, Stop, Build, Verify, Improve automations, Update docs. Next: see the agent-facing details in Agent details.