Skip to content

v2.5.2 — Codex fallback runs stay tracked

Latest

Choose a tag to compare

@PythonShe PythonShe released this 23 Sep 15:34
· 2 commits to main since this release
30d20ad

Codex fallback runs stay tracked. Every skill with a cross-model Codex seat falls back to the bare codex exec CLI when the plugin's companion script isn't found, and that fallback ran with -s read-only --ephemeral. --ephemeral tells Codex not to write its session rollout under ~/.codex/sessions, and local usage trackers (the tokens CLI and similar) count Codex usage only from those rollouts. So every fallback Codex review or investigation spent real quota without showing up in local usage stats. A Coda run in a downstream project surfaced it: its whole-PR Codex review used about a tenth of a five-hour window, and the local record showed nothing.

The fallback shape drops --ephemeral everywhere it appeared: the shared reviewer contract (shared/codex-reviewer-core.md), the canonical statement in shared/invariants.md, and Tuner's investigator fallback. The contract now says not to add the flag back, and why. -s read-only still keeps Codex from editing the tree, and < /dev/null, the prompt and verdict files and the timeout are unchanged. Routing surfaces are unchanged, so no eval re-run is needed. Run /plugin marketplace update to pick it up.