Skip to main content
Open the app, pick a repo, choose your agent, and keep moving. The first win is simple: get one useful agent session running without leaving a trail of terminal tabs behind.
Placeholder image: Neroli opening into a repository with New Session, provider picker, TUI pane, and session status visible.

The first-run flow is repo, provider, session, panes, and work in motion.

​
Install and connect

You need:
  • macOS 15.6 or later
  • a local Git repository
  • at least one coding agent, such as Claude Code, Codex, or OpenCode
  • GitHub authentication if you open pull requests from your workflow
Open Neroli, choose a repository, and start a session with the provider you want for that job. The app creates an isolated workspace for the run and launches the provider TUI directly inside the UI.

​
The first loop

1

Open a repo

Neroli turns the repository into a workspace for sessions, panes, automations, and cloud handoffs.
2

Launch an agent

Start Claude, Codex, OpenCode, or another provider from a new isolated session. Mix providers when different jobs need different strengths.
3

Stay in the real TUI

Use the provider interface directly inside Neroli, with the same behavior and new features you expect from the terminal.
4

Add panes as needed

Attach terminals, browsers, simulator, diffs, file viewers, and generated artifacts to the session instead of juggling separate windows.
5

Run more sessions

Spin up more agents for features, experiments, cleanup, docs, or review without mixing their files.
Neroli keeps attention visible as work runs. You can see which sessions are running, which ones need approval or input, which checks failed, and which work is ready to review.

​
Your first hour

Use the first hour to make the workspace feel smooth. You can add deeper setup later.
1

Run one real task

Start with a task you would have given an agent anyway. Watch how the TUI, worktree, panes, and status stay together.
2

Add one verification pane

Open the browser for a web flow, the simulator for an iOS flow, or a diff/file viewer for generated output.
3

Create Run and Verify

Add the two automations you will use constantly: one to start the app, one to check the work.
4

Start a second session

Run a docs update, review pass, experiment, or test improvement in parallel so the isolation becomes obvious.
5

Move sessions on the board

Use Planning, In Progress, In Review, Merge, and Done to track where each session stands.
6

Ask for self-review

Have the agent summarize the change, run checks, inspect its diff, and fix obvious issues before you review.

​
A simple prompt

Add screenshots, routes, logs, or files when they help. Neroli’s job is to keep the session organized while the agent works.

​
Make the workspace better

Manual launch is enough for day one. Once a repo becomes a workspace, add automations that prepare sessions, copy env files, assign ports, run dev servers, stop stacks, verify changes, and launch agentic helpers. You can ask an agent to set those up. The Neroli CLI is mostly for agents and automations, so they can discover the current session, panes, browsers, simulator, and existing actions without guessing. Next: understand the core model in Concepts, manage parallel work with the Session board, then make every new session easier with Automations.