Jobs

The job stream panel — how to browse, filter, and inspect every job dispatched from Linear, including live status updates and the full job detail view.

The Jobs panel (/home/jobs) is the central log of every piece of work Delego has received from Linear. Jobs are created automatically when you delegate an issue — you don't create them manually. The panel gives you visibility into what's running, what needs attention, and what has already finished.

Job stream

The stream shows all jobs grouped by day with headers marking Today, Yesterday, and older dates. Each row shows:

A colour-coded status pill indicating the current state.
The Linear issue identifier in monospace — e.g. ENG-42.
The repository slug the job is targeting, or an unmapped label if no repository was resolved.
The issue title, truncated to a single line.
A timestamp — time only if the job is from today, date and time otherwise.

Clicking any row opens the job detail page.

The stream updates in real time — you do not need to refresh the page to see jobs progress from queued to running to completed.

Filtering by state

A pill tab bar above the stream lets you narrow the list to a specific state. The available filters are:

Filter	What it shows
All	Every job, regardless of state.
Queued	Jobs waiting for a runner to pick them up.
Running	Jobs currently being executed by a runner.
Waiting for input	Jobs paused because a required label is missing or conflicting.
Completed	Jobs that finished successfully.
Failed	Jobs that ended in an error.
Cancelled	Jobs that were cancelled before completion.

Each tab shows a count badge. You can also link directly to a filtered view via the ?state= query parameter.

Job states

A job moves through the following states during its lifecycle:

State	Meaning
`queued`	Enqueued and waiting for a runner.
`running`	Claimed by a runner; the agent is actively working.
`completed`	The agent finished and (optionally) pushed a branch or opened a PR.
`failed`	The agent encountered an error it could not recover from.
`waiting_for_input`	A required execution preference (executor, model, or repository) could not be resolved — or the agent paused mid-execution to ask the user a question.
`cancelled`	Manually cancelled from the job detail page.

Job detail

Clicking a job row opens the detail page for that job. It is divided into a main content area and a right rail.

The topbar shows the Linear issue identifier as the title and the issue title as the subtitle. On the right: the current status pill, an Open in Linear link, and an actions menu.

Prompt tab

The first tab shows the agent prompt summary — the text the agent received from the Linear issue. If the job has failed, a failure summary appears in red. If a pull request was created, the PR URL is shown as a clickable link. If a commit was made, the commit SHA appears in a code block.

Timeline tab

The Timeline tab shows every state transition the job has passed through, in reverse chronological order. Each event shows:

The event type.
The actor — runner, user, or system.
A timestamp down to the second.
A plain-text summary of what happened.

Events are marked with coloured dots: green for completed, blue for the current state, gray for pending.

Communication logs tab

The Communication logs tab shows the low-level record of every API call the relay made on behalf of the job — Linear webhooks received, Linear Agent Session status updates sent, runner API calls, and GitHub API interactions. Each entry shows the channel, direction, status, and a summary.

This tab is most useful when debugging a job that failed unexpectedly or a PR that did not get created.

Right rail

The right rail shows two cards:

Overview — repository slug, the runner that claimed the job (or "Unassigned"), the attempt ID, and timestamps for when the job was queued, started, and finished.

Execution preferences — the resolved values for executor, model, and thinking mode, each annotated with the source that determined it (issue label, project label, workspace default, or unset).

Actions

The actions menu in the topbar gives you three operations on a job:

Cancel — stops a queued or running job. The runner will not pick it up (or will stop after the current step if already running).
Requeue — creates a fresh attempt for a failed or cancelled job.
Archive — hides the job from the stream. Archived jobs are not deleted.