Jobs
Nearly everything the platform does happens as a job: discovery, to-be generation, implementation, merges, test runs, index refreshes. The Jobs page is where you find out what is happening, what is waiting on you, and what went wrong.
The groups
Every job status is in exactly one group, and none is hidden. That is deliberate — a job in no group would be a job doing work you cannot see.
| Group | What it holds |
|---|---|
| Queued | Accepted, not started |
| Running | In flight now |
| Needs attention | Stopped and waiting on a person |
| Open | Started, neither finished nor waiting |
| History | Finished, whatever the outcome |
Finished background polling jobs are hidden from the list. They are how the platform keeps itself up to date, they run constantly, and showing them would bury everything else.
Needs attention
This is the group to read first, because it is the one that will not clear itself. A job lands here when it needs something only you can supply — most often a preflight answer, a decision, or a clarification where your installation has agent questions enabled.
Cancelling
You can cancel a running job.
- Cancelling is recorded as cancelled, not failed. The history distinguishes "we stopped this" from "this broke", which matters when you are looking back at why a feature took three attempts.
- Cancelling a feature's background job leaves the feature's status untouched. Stopping a job is not a statement about the feature it was working on.
- An interrupted implementation is paused, not ended — see Implementing a feature.
Agent Logs
Jobs tell you what ran. Agent Logs tells you what an agent did: a single timeline of its steps, the files it touched, and what it said along the way.
Some specifics worth knowing when you are reading one:
- The log lists jobs, not agent sessions, so a job that resumed is one entry rather than several.
- Background poll jobs are hidden here too.
- Token usage is on a card you can collapse.
- A resumed run's log shows the session it continued, rather than starting blank.
When a job fails
Read the failure message first — the platform tries hard to make failures say what actually happened rather than surfacing a stack trace. A provider error inside an agent container stops the job and reports the provider's own error, and a run that stops for a recoverable reason resumes rather than failing.
A completed feature surfaces its latest job failure whatever the job was, so a feature that looks finished but has something broken behind it says so on the feature itself.
Next: Project settings.