Skip to main content
Three commands for managing background Codex jobs: check what’s running, retrieve finished output, and cancel active tasks.
If you omit the job ID, all three commands operate on the most recent job for the current repository.

​
/codex:status

Shows running and recent Codex jobs for the current repository.

​
Syntax

/codex:status [job-id] [--all] [--wait] [--timeout-ms <ms>]

​
Flags

​
job-id
string
Show detailed status for a specific job. If omitted, a summary table of recent jobs is shown.
​
--all
boolean
Include all jobs, not just the most recent ones.
​
--wait
boolean
Wait for the specified job to complete before returning. Requires a job ID. Useful in scripts or when you want to block until a background job finishes.
​
--timeout-ms
number
Maximum time in milliseconds to wait when using --wait. Defaults to 240000 (4 minutes). If the job does not complete within this time, the command returns the current status without an error.

​
Examples

/codex:status
/codex:status task-abc123
/codex:status task-abc123 --wait
/codex:status task-abc123 --wait --timeout-ms 120000

​
Use cases

  • Check progress on a background review or rescue task
  • See the latest completed job and its outcome
  • Confirm whether a task is still running before starting another

​
/codex:result

Shows the final stored Codex output for a finished job. When available, it also includes the Codex session ID so you can reopen the run directly in Codex with codex resume <session-id>.

​
Syntax

/codex:result [job-id]

​
Examples

/codex:result
/codex:result task-abc123

​
/codex:cancel

Cancels an active background Codex job.

​
Syntax

/codex:cancel [job-id]

​
Examples

/codex:cancel
/codex:cancel task-abc123