Codex CLI

Codex CLI is a first-class LoopX host. The preferred product path starts with one visible TUI message; headless execution remains an explicit fallback or a bounded partner path rather than the default user experience.

Start And Install

• TUI-first LoopX loop: one visible TUI message starts LoopX, with session-attached automation as the preferred follow-up.
• Packaged install: no-clone install, update, and start path; clone-plus-canary remains a contributor route.
• First-run rehearsal: connects no-clone install, one-message TUI bootstrap, and proof-capture fixtures.
• No-clone release verification: proves installer, bootstrap message, bundle, and proof fixtures stay aligned.
• LoopX Turn quickstart: the bounded isolated-headless path with one adapter, one validator, one command, and typed outcomes.

Visible Session Evidence

• Codex CLI live TUI first-message pilot: records why manual paste remains primary until visible completion is proven.
• Visible proof-capture protocol: opt-in procedure for turning resume or remote-control signals into public-safe evidence.
• Visible attach proof pilot: the bounded acceptance path for proving a resumed session is the intended one.
• Proof-capture demo: sample fixtures and acceptance decisions without running Codex or reading session material.
• Same-open-TUI continuation observation: current evidence for visible first-turn continuation and the remaining scheduled-attach boundary.

The Codex CLI bounded visible pilot adapter is the public-safe packet command covered by examples/codex-cli-bounded-visible-pilot-adapter-smoke.py. It validates first-response and runtime-idle fixtures before a live TUI bootstrap can count as successful.

The Codex CLI visible first-response capture plan is the copy-first packet command covered by examples/codex-cli-visible-first-response-capture-plan-smoke.py. It produces public-first-response.json and public-runtime-idle.json without argv prompt leakage or raw transcript reads.

Scheduling And Automation

• Automation driver audit: keeps TUI bootstrap primary, composes quota/idle/fallback checks, and treats codex exec as an explicit fallback.
• TUI continuation priority: keeps same-open-TUI continuation ahead of frontstage or showcase support work when both are runnable.

Stable host and turn schemas remain under docs/reference/protocols/.