One entry per run

Jobs and logs

Every long-running piece of work appears under Jobs with its state and its log.

What gets an entry

Every long-running piece of work

  • A goal or ultracode run
  • A research run
  • An import or export
  • A website build

appears under

Jobs

  • its state
  • its log

Each entry carries its log, not just a status line. The list shows your latest 100 entries. Finished maintenance runs, such as the background summaries of long chats, are hidden behind a toggle that names how many there are and what they cost.

From running to what it cost

States of a jobA job waits in the queue, then runs while its log grows. It ends as done, with log and cost kept, or as failed, with the reason. An error in a goal or ultracode run schedules a retry, up to ten times. A run stops as paused when credit runs out, when an approval or guardrail is needed, or when you cancel it. A paused run goes back to the queue when you resume it.error: retry,goal and ultracodeout of retries,or other typesno credit, approval,guardrail, your CancelResume or Let itcontinueQueuedRunninglog grows liveDonelog and cost stayFailedwith the reasonPaused
Every job moves between a few states; a paused job waits for you and re-enters the queue when you resume it.
Diagram as text
  1. A job starts as queued.
  2. It runs, and its log grows while you watch.
  3. A finished job is done. Its log and cost stay on the entry.
  4. An error in a goal or ultracode run schedules a retry: after 2 minutes, then 4, then every 5, up to 10 tries. Other job types fail at the first error.
  5. A job that fails shows its reason on the entry.
  6. A job pauses when credit runs out, when it needs an approval, when a guardrail trips, or when you cancel it.
  7. Resume, or Let it continue, puts a paused job back in the queue. For a tripped guardrail you can grant extra iterations or extra budget.

While it runs

Follow it live

You can follow a running job live, reading the log while the work is still happening. Cancel run stops it after a confirmation; a stopped job is paused, not lost.

the run ends

After it ends

Read it afterwards

The log stays with the job once the run is finished, so you read it afterwards instead of catching it in the moment. Open an entry to see its trace: model calls, shell commands, tokens, time and cost, and how many requests the broker denied. You can download the trace as JSON. A failed job shows why it failed.

Per job

What it cost

Cost is attributed per job, so you can see what a particular run actually cost.

A job that stopped because credit ran out, an approval is needed or a guardrail tripped waits as paused. Resume puts it back in the queue; for a guardrail you can grant extra iterations or budget. Goal and ultracode runs that hit an error retry on their own, up to 10 times.