Repository navigation
v2.5.1 — Codex fallback stops hanging
The Codex fallback stops hanging. Every skill that seats a cross-model Codex agent falls back to the bare codex exec CLI when the plugin's companion script is absent, and that fallback has been quietly the least reliable seat in the line: codex exec drains stdin to EOF whenever stdin is not a TTY — prompt argument or not — and a subagent or background shell hands it an open pipe nobody writes to, so the process wedges forever at 0% CPU with at most Reading additional input from stdin... on the log (upstream openai/codex#20919, still open, no --no-stdin flag). Six separate runs in a downstream project hit it between June and September, and it is the hang that cost Jam its Codex seat in v2.3.0. The cure was found and re-found by hand each time; this release writes it down once. The shared contract's fallback becomes one exact shape — prompt written to a scratchpad file, -o verdict file, -s read-only --ephemeral, < /dev/null on the call, the Bash tool's ~10-minute timeout, foreground inside a background subagent, never in the conductor's own Bash call, because a hung codex exec blocks whoever ran it until a timeout fires or a human interrupts, and in the conductor's hands that is the whole run stalled — with the empty-output-is-failure rule extended to it, the stdin line named as the hang signature, and no relaunch: a second attempt doubles the wall-clock the panel already paid, so the shape has to be right on the first try. Tuner's investigator fallback, which until now told the conductor to run a bare codex exec in a background Bash call — the exact recipe for the hang — is rewritten as a marked copy of the same shape, and shared/invariants.md gains the canonical statement so the two cannot drift. The README's Codex prerequisite says the same in one sentence. Routing surfaces unchanged; no eval re-run needed.