ADR 015 Unavailable Live Codex Observation

• ID: ADR-015
• Status: Accepted
• Date: 2026-08-24
• Date meaning: Original dated decision/source section; extraction recorded 2026-10-02.
• Implementation: No implementation information was recorded in the source status; tickets own progress.
• Approval qualification: Recorded accepted decision; dated delivery conditions are historical, not new execution authorization.

Context

This records the bounded live-observer feasibility outcome for the inspected desktop transport, not a claim about later unrelated sessions.

Recorded feasibility outcome

Codex CLI 0.147.0 documentation and command help describe app-server clients connecting through the transport selected when that app-server process starts. The running Codex desktop app starts its app-server without an explicit listener, which selects the parent-owned standard-input/standard-output transport. Process and listener inspection found no supported named Unix or TCP listener through which a separately sandboxed Release Radar process could authenticate and attach to that already-running desktop task. Starting another app-server process would not prove access to the desktop process's live task state.

The shared live-observation gate is therefore blocked. Release Radar does not implement an app-server client, helper, or private-state reader for RR-05. It retains the stable CodexObserver contract and normalized thread/goal models, but its configured observer explicitly reports unavailable; an injected last-known snapshot is always downgraded to stale. Neither state may be presented as live or mutate a formal delivery lane. This is the approved degraded dependency outcome for continuing to RR-07 after independent RR-05 review.