Get run details
Retrieve detailed information about a specific agent run, including the full prompt, session link, and resolved configuration.
Path parameters
The unique identifier of the run
Response
Run details
Unique identifier for the run
Unique identifier for the task (typically matches run_id). Deprecated - use run_id instead.
Human-readable title for the run
Current state of the run:
- QUEUED: Run is waiting to be picked up
- PENDING: Run is being prepared
- CLAIMED: Run has been claimed by a worker
- INPROGRESS: Run is actively being executed
- SUCCEEDED: Run completed successfully
- FAILED: Run failed
- BLOCKED: Run is blocked (e.g., awaiting user input or approval)
- ERROR: Run encountered an error
- CANCELLED: Run was cancelled by user
Where the run executed:
- LOCAL: Executed in the user's local Oz environment
- REMOTE: Executed by a remote/cloud worker
The prompt/instruction for the agent
Timestamp when the run was created (RFC3339)
Timestamp when the run was last updated (RFC3339)
Total runtime as an ISO 8601 duration (e.g. "PT2M30S"), computed server-side from run executions.
Timestamp when the agent started working on the run (RFC3339)
Source that created the run:
- LINEAR: Created from Linear integration
- API: Created via the Warp API
- SLACK: Created from Slack integration
- LOCAL: Created from local CLI/app
- SCHEDULED_AGENT: Created by a scheduled agent
- WEB_APP: Created from the Warp web app
- GITHUB_ACTION: Created from a GitHub action
- CLOUD_MODE: Created from a Cloud Mode
- CLI: Created from the CLI
- JIRA: Created from Jira integration
- SELF_IMPROVEMENT: Created by Warp's self-improvement pipeline
- GITHUB_WEBHOOK: Created from a GitHub webhook event
- GITLAB_WEBHOOK: Created from a GitLab webhook event
- AUTOFIX: Created by Warp's autofix pipeline
- RUN_SCORER: Created by Warp's run-scoring judge
- ORCHESTRATION: Created as a child run by the orchestration layer (parent_run_id set)
UUID of the shared session (if available)
URL to view the agent session
URL to the run trigger (e.g. Slack thread, Linear issue, schedule)
UUID of the conversation associated with the run
UUID of the parent run that spawned this run
Custom key/value metadata attached to a run at creation time and immutable afterward. At most 20 keys. Keys are 1-64 bytes matching [a-zA-Z0-9._-]+ (case-sensitive); values are 0-256 bytes of UTF-8 and cannot contain NUL characters. Requests with invalid metadata are rejected. A run's effective metadata is merged per key at creation: explicit request keys override keys inherited from the parent run, which override automatic keys (ticket_id and ticket_source on Linear- and Jira-triggered runs).
Whether the sandbox environment is currently running
Whether the run's type is eligible for cancellation via the API. State-independent: false for GitHub Action and local runs; true for all other run types (including self-hosted). Clients should still gate the control on the run's current state.