Periodic session progress

Settings → Session status controls server-side progress questions for your running sessions. Updates are enabled by default, with a 15-minute interval. Disable them or choose any integer interval from 5 to 1440 minutes. Saving applies without restarting sessions or replacing containers.

The host asks a supported working agent what it is doing and what remains, using its native background-question interface. The short answer requires no tools or actions and leaves the main task running. Questions use the agent account's quota; this feature does not call a Decisions API.

Display

Projects shows STATUS · date/time · answer below session headings in the container/repository tree and Mosaic. TUI, web and desktop share this component. Dates are UTC (MM-DD HH:mmZ) and identify when the answer was captured, separately from the live working/input/quota state. The previous answer and date remain visible during refresh or after failure. A new process generation cannot inherit an old process's status.

The header hides legacy probe failures for clients whose background mechanism is unsupported. For example, a saved Codex /side timeout does not remain a current warning after automatic Codex probing has been disabled. Native working, input and permission states remain independent of these optional summaries.

Supported mechanisms

Agent Mechanism Running version gate
Claude Native /btw; completed answer overlay 2.1.212
Codex Automatic probing disabled: /side changes the visible interactive terminal Unsupported
Other clients No automated probe until both safe execution and response capture are verified Unsupported

Sources: Claude side questions, Codex commands. Antigravity documents /btw, but its renderer/return path is not yet verified for safe automation. An available slash command alone is insufficient. Unknown or older running CLI versions are not probed; installing a newer CLI does not update the version of an already running process. Unsupported clients never receive an ordinary task prompt in place of a background question.

Scheduling and input

The execution host schedules checks independently of TUI, browser and laptop connections. Policies and attempt times persist across controller restarts; at most two probes run concurrently per host. Fresh native working state, an eligible account and exact workspace, conversation and process identities are required.

Questions, permissions, compaction, exhausted quota, recovery, Overnight, attached terminals, any session sharing grant or active public link, and an occupied composer defer probing. Read-only observers count as viewers too. An incoming terminal attachment waits, with progress, until an admitted probe closes its view; previews are deferred during that short reservation. The existing input reservation prevents competing deliveries. Paste and Enter are separate events; the exact automation draft is rechecked before submission. Other text is never cleared. Runtime input delivery also shares a per-session lock with approvals, environment notifications, handoff and automatic compaction. Policy files are updated immediately even when their notification must wait for input access.

Only a complete, correlated answer inside the recognized native side view is accepted. Echoes, queued questions, partial JSON and unrelated output are not status reports. Closing Claude’s readonly overlay requires its exact question nonce, native close/copy footer and unchanged process/conversation identity. The same verified Escape close is allowed if the answer times out. A probe has a 20-second budget, including cleanup; it never sends Ctrl+C. Mixed or unrecognized terminal state receives no close key and produces an explicit failure asking the operator to inspect the session. Durable receipts prevent uncertain deliveries from being replayed. If submission or overlay cleanup is unconfirmed, that session is paused across intervals and controller restarts instead of accumulating more questions. The managed question stays short and includes only a correlation nonce and requested response format. It does not clear native question history.

Settings → Session status identifies held sessions. After checking the session, select Resume status checks (Enter or r). Resuming verifies the current conversation, process generation and reservation, then starts a fresh quiet interval. It does not enable a globally disabled policy or submit another question immediately.

Codex /side is not a safe background interface: it opens a side conversation in the visible terminal. Automatic Codex status requests are therefore disabled, even when the CLI supports that command. Legacy side conversations remain excluded from parent lifecycle and identity tracking after a request expires.

API and MCP

Method Route Scope
GET /v1/session-work-status/settings Current console user's policy and agent support
PUT /v1/session-work-status/settings Current user's {enabled, intervalMinutes} policy
POST /v1/session-work-status/sessions/:sessionId/resume Resume your held session using its current reservation, native session ID and process generation

Authenticated session summaries contain workStatus: state, bounded text, capture/attempt dates and process generation. Agent-only result submission also verifies the execution host and active input reservation. Text is sanitized; terminal histories, prompts and credentials are excluded. Public links cannot change status settings.

inspect_current_project exposes the authenticated session's own last snapshot. Operator MCP clients discover the settings through controller_operations and call controller_request under the same ownership rules as the console. Project agents cannot change another user's policy or submit another session's results.

Diagnosing missing updates

Settings → Session status lists the recent host checks for running sessions, including a failed attempt's stage. Diagnostics contain only a bounded stage such as identity, integration, composer, submission or waiting for an answer; terminal output and exceptions are never forwarded. A configured interval does not prove a successful /btw response. Only a captured, correlated answer is shown as available.

Native conversation changes within the same process are reconciled only from owned live process evidence. Codex uses its current canonical rollout file descriptor whose native ID also agrees with the root hook; forked/side metadata is rejected unless explicitly resumed as the main conversation. Claude uses a root hook's ancestor PID and process start identity. Child and temporary side conversations cannot replace the parent. A verified change clears the old model, context, goal, status and completed-task marker. A missing identity proof remains an explicit safe hold until a new native event provides it; devctrl does not guess another account's newest transcript.

The background-answer parser was also checked against an isolated official Claude 2.1.302 session with a synthetic /btw status question and native answer overlay. This verifies the native primitive; it does not certify that every production session is eligible or that a scheduled probe succeeded. Production checks still require their own correlated result.