Skip to main content
The left sidebar is how you keep many agent sessions from turning into a blur. Treat it like a small issue tracker for work that is happening inside Neroli. Each row is a session. Each group is a stage. Drag sessions between groups as the work changes.
Placeholder image: the Neroli sidebar with Planning, In Progress, In Review, Merge, and Done groups, plus automation buttons on group headers.

The session board keeps parallel agent work organized by stage, with group actions for automations.

The groups

New or unplaced sessions appear in In Progress by default. Move them wherever your workflow needs them.

A practical loop

1

Plan

Keep early sessions in Planning while the agent is exploring, drafting, or asking clarifying questions.
2

Build

Move the session to In Progress once it is doing the work.
3

Review

Move substantial changes to In Review. Ask the agent to self-review, run checks, and collect evidence.
4

Prepare to merge

Move work to Merge when it looks ready but still needs your final validation.
5

Close it out

Move validated work to Done, or archive/delete it when you no longer need the session around.
This is deliberately lightweight. The board does not need to mirror your GitHub issues exactly. It is there to keep active agent work understandable.

Automations in the board

The board is not just visual. Automations can attach to sidebar groups.
  • A group header can show automation buttons for that stage of work.
  • A group automation receives the group name and the sessions in that group.
  • A Session moved automation can run when you drag a session into a new group.
  • Agents and automations can inspect a session’s group and, when allowed, move a stopped or failed session to another group.
Useful examples:

Keep it useful

Use the sidebar as a living map of what you are paying attention to. The groups are there to help you decide what deserves review, what is ready to land, and what can disappear from view.
  • Keep uncertain work in Planning or In Progress until the next step is obvious.
  • Use In Review when you want the agent to review its own work and surface risk.
  • Use Merge for work that looks ready and needs your final pass.
  • Use Done when you want completed work to stay visible before you archive it.
If a session is noisy, stale, or no longer useful, archive it. If a group keeps collecting the same kind of manual work, turn that pattern into an automation. Next: make group actions repeatable with Automations.