Skip to main content
When an agent misbehaves, you need to know what its harness actually had: which plugins and skills it loaded, whether an MCP server connected, how full the context is, and which subagents are still running. paddock collects that state from inside the harness, in one shape for both harnesses, and gives it to you with the session’s events.

Where it comes from

  • At every turn’s end, while the harness still runs, paddock stores a snapshot as a session.status event, just before the turn’s turn.ended. It is part of the session’s history.
  • Between snapshots, live changes, such as a subagent’s progress, an MCP server finishing its start, or the context filling, arrive on the stream as status.update events. They are never stored or replayed; each carries whole sections, so the next one supersedes a missed one.
In the browser, the client SDK keeps the latest status for you in harnessStatus: the newest snapshot with every later update applied. It is null until the session’s first turn has ended.
On your backend, read the latest snapshot from the session’s events:
With neither after nor before, events.list returns the latest events, so a limit of 1 returns the newest snapshot.

The sections

A status has six sections, in this order. Codex has no Workflows section. Each entry of Plugins, Skills, MCP, and the definitions carries a scope that says where the harness found it: home (the configuration paddock rendered from the agent), project (the session’s working directory), plugin (contributed by a plugin, named in plugin), or builtin (shipped with the harness). It carries a state, loaded, starting, or error, and the harness’s error message. Context is marked estimated when the harness estimated counts locally instead of counting them; a section the harness does not report is null. The status names no configuration values: no MCP URLs, headers, commands, or environment values.

Status and configuration together

The status says what the harness made of the agent’s configuration. Join it with the agent’s capability entries by name to see both:
  • An entry the agent has but the status lacks has not been loaded, or is still pending.
  • A row is pending while the session’s harness has not taken the entry’s latest change: the entry’s generation is above the generation of the session’s latest config.applied. See Capabilities.
  • A status entry of scope home that the agent no longer has was removed and is pending until the harness drops it.
The console’s Status tab, in the Playground and on every session’s page, shows exactly this join, and lets you install, disable, and remove plugins and MCP servers from it. See Console.

When there is no status

Nothing is collected while no harness runs: before a session’s first turn, and while the agent sleeps, the latest stored snapshot stands. A turn whose harness had already exited has no snapshot.