Where it comes from
- At every turn’s end, while the harness still runs, paddock stores a snapshot as a
session.statusevent, just before the turn’sturn.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.updateevents. They are never stored or replayed; each carries whole sections, so the next one supersedes a missed one.
harnessStatus: the newest snapshot with every later update applied. It is null until the session’s first turn has ended.
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
generationis above the generation of the session’s latestconfig.applied. See Capabilities. - A status entry of scope
homethat the agent no longer has was removed and is pending until the harness drops it.