Skip to main content

State & Metrics

Core orchestrator state, runtime metadata, real-time events, and observability.
POST /api/v1/refresh returns 202 Accepted, not 200. The reconciliation runs asynchronously.

Issue Management

Inspect individual issues, control running agents, override models and templates, and transition issue state.
The :id parameter is the Linear issue identifier (e.g. ENG-123).

Model Override

string
required
The model identifier to use for this issue (e.g. o4-mini, gpt-4.1).

Mid-Turn Steering

string
required
Guidance text injected into the running agent’s context.

State Transition

string
required
Target state name. Use GET /api/v1/transitions to see valid transitions.
string
Optional human-readable reason for the transition.

Attempts

Each issue can have multiple attempts. An attempt represents a single agent execution run.

Configuration

Read the effective merged config, inspect the schema, and manage runtime overlay overrides.
The overlay is persisted to disk and survives restarts. It merges on top of the base config file and environment variables.

Secrets

Manage runtime secrets without restarting the service. Secrets are encrypted at rest.
GET /api/v1/secrets returns key names only, never the secret values.

Templates

Manage prompt templates for agent instructions. Templates support variable interpolation.

Workspaces & Git

Inspect and manage the working directory pool and git routing context.

Audit

Paginated audit log of all orchestrator actions for compliance and debugging.

Notifications

Persistent notification timeline for run lifecycle alerts. Backed by the notification store and deduplicated per run.
The test endpoint reuses the Slack webhook configured under notifications.channels in your config overlay. See Notifications setup for channel configuration.

Automations

Scheduled background automations — scheduler inspection and on-demand runs.

Alerts

Alert delivery history — each row records a rule evaluation, trigger, or cooldown event.

Webhooks

Inbound webhook receivers for external integrations and an authenticated trigger dispatcher.
Inbound receivers (/webhooks/linear, /webhooks/github) have a separate rate limit of 600 requests/minute. Configure the webhook URL in the corresponding provider’s workspace settings. POST /api/v1/webhooks/trigger requires the configured trigger credentials.

Codex Operator

Operator routes that proxy to the embedded Codex control plane. Each route forwards to a JSON-RPC method on the Codex app-server session. See Runtime concepts for context on the control-plane session lifecycle.

Session state

MCP servers

Threads

Account

Interactive input

All Codex routes return 503 when the control plane is not configured or is unreachable, 502 when the underlying Codex request fails, and 501 when the requested method is not supported by the installed Codex version.

Docs & Spec

Machine-readable API specification and interactive documentation.

What’s Next

Last modified on April 10, 2026