# Long coding jobs

> A big coding job that runs by itself in the background, with a planner, several workers at once and a judge who checks it. How to start one, what you see while it runs, how to guide or stop it, and what it costs.

Building software · Updated: 2026-11-11 · version 2.0.273 · https://nobreiniers.com/en/help/long-work/

A long job is for big work: moving a project to a new version, a feature that touches many files, a large fix with tests. The agent splits it among several helpers who work at the same time, in the background, and you carry on with your chat. For a small change you do not need it: the agent just does it.

## How it works, in plain words

1. **A planner** splits the objective into tasks that make sense on their own. If an area is large, another planner splits it in turn.
2. **Workers** take one task each, all at the same time, each in its own copy of the project, without coordinating with each other. Each finished task is merged into the job's branch; if two clash, it goes back to the worker who made it to sort out.
3. **The tests**, if you gave a command to run them, run before anything changes and after every round, and the job never accepts fewer passing tests than it already had.
4. **A judge who did none of the work** decides when a round has nothing left: finished, another round with its own focus, or stop.
5. Anyone who runs past the time they had is stopped and their planner splits the task.

All of them use the model of the chat that started it: the judge has no model of its own.

## Start one

1. Open a chat in your project. A long job starts from a chat of yours, not from a helper or an automatic task.
2. Tell it what you want and the result you expect: "move this project to the new version and keep the tests passing", "fix this bug everywhere in the project". If you like, tell it how the tests are run and ask it to do this as a long job.
3. The agent decides how to start it: the objective, the conditions for calling it finished, and the test command. If the test command needs your review, the job does not start and the agent tells you.
4. With «Project only» you get a card saying it wants to start «a long task that works by itself», with the objective. Approve it to start. With «Full access» there is no card: your order is enough. With «Read only» it does not start, because it changes files; change the permission and ask again. See [Permissions, approvals and your rules](https://nobreiniers.com/en/help/approvals-and-rules/).

Worth knowing before you start:

- **It starts from what you have already committed** (the last commit of your project). Changes you have not committed do not go into the job.
- **With git, they work at the same time.** 3 at once by default, up to 10; the agent can ask for another number. If the folder is not a git project, or it is a Nobreinier's, one works at a time in that same folder.
- **It has limits you can change by asking:** 5 rounds by default (up to 50) and 45 minutes per task (from 5 to 480).
- **Up to 12 long jobs at once.** With 12 running, the agent tells you to let one finish or stop one.

## What you see while it runs

Above the message box, in the chat that started it, a card shows the job's name and, beside it, how it is going, for example: "Working · round 1/5 · 2 of 6 done · 3 working · tests ✓ 12/12". The phase says «Planning», «Working», «Testing» or «Judging».

1. Click the name (its tooltip says «Show the task tree») and the tree opens: each row is a task with who does it («Planner», «Worker» or «Judge») and how it is going («waiting», «ready», «working», «done», «failed» or «blocked»).
2. Click a task that already has someone working on it and you see what they do or did.
3. When the judge asks for another round, the card says so with its reasons: «The judge asked for another round».
4. When it ends, the card says «Finished» or «Did not finish», with the name of the branch where the work stands. A notice appears, «Long work finished» or «Long work stopped», and the chat gets a note with the tasks done and failed, the tests and how many files changed. Breini tells you how it went.
5. A few seconds after it ends, the card folds to its chip (see [A tour of the window](https://nobreiniers.com/en/help/tour-of-the-window/)). The card stays at hand for a day.

## Guide it, pause it or stop it

While it runs, the card has three buttons:

- **«Pause»**: whoever is working finishes their step and the job waits. «Resume» carries on.
- **«Give a note»**: write what it should take into account (up to 4000 characters) and press «Send». Whoever is working at that moment reads it at their next step, and so do the next planners and the judge. It corrects the course without starting over.
- **«Stop»**: stops the job. What was done stays on its branch.

These buttons belong to the job, not to the chat. To stop the job, use its own «Stop». If you close the app, when you open it the job goes on where it was: tasks that were half done pick their work back up.

## Where the result ends up

In a git project, the job does not touch your files while it runs: what it does stays on a separate branch of your project, with a name that starts with `osiris/job-`, in its own folder. Without git, it works in your own folder. When the job ends, the agent tells you the branch and how to bring it into your folder. Ask it to merge it into your project once you have looked; with «Project only», merging asks you first. See also [Code review](https://nobreiniers.com/en/help/code-review/).

## What it costs

- **The price before it starts**: choose «Long job» in the «+» menu of the message box and finish the sentence it writes. The assistant is asked to lay the job out on a card with its steps and an estimated cost on your model, and from that card the job starts only when you press «Start» («Not now» puts it away). Started any other way, the approval card shows the objective, not a figure.
- **Every planner, worker and judge is a conversation with the chat's model**, so it spends from the same account and shows in your balance like everything else ([Your balance and the status bar](https://nobreiniers.com/en/help/title-bar-usage/)).
- **More workers at once, more rounds or longer tasks, more spending.** To spend less, ask for fewer workers or fewer rounds, or stop the job.
- **A spending limit includes it.** `/budget` counts the chat's helpers, including a long job's ([Stop, steer or queue](https://nobreiniers.com/en/help/stop-and-steer/)).

## If something goes wrong

- **The agent says there are already 12 long jobs running**: wait for one to finish or stop one with its «Stop».
- **It says the test command needs your review**: give a plain test command and ask again.
- **«Did not finish»**: read the judge's reasons on the card. What was done stays on its branch; you can give a note and ask it to go on.
