OpenClaw issue #119971 records a concrete failure: a Codex app-server session crossed its budget, emitted an intentional “app-server owns automatic compaction” result, and then rejected the user’s message before a model call ran. That is the wrong way for a long conversation to become difficult. It should trim what it can, preserve useful state, and keep the next message moving—not drop the turn.
That sequence matters because the system had decided compaction was required. A result shaped like success—ok: true, but compacted: false—was only safe if something else had already done the recovery. Here, the reply-preflight path had not asked Codex to perform a non-manual native compaction, then treated the resulting skip as a hard failure. The public issue traces the mismatch from the budget gate to the user-facing error.
A name for the handoff
The fix in PR #120197 does more than bless the skip. It labels the request required_preflight, routes it through OpenClaw’s private native-compaction bridge, and asks the Codex app server to begin compaction. The accompanying commit and tests make the distinction visible: a required preflight records its origin and calls the native thread-compaction endpoint; a binding that changes underneath it becomes an explicit stale-binding failure so the existing context engine can take over.
That is a more demanding rule than “don’t error on a no-op.” If a preflight is mandatory, quietly accepting an uncompacted thread only hides the next failure. The patch also keeps its escape hatch narrow: the special recovery is for missing or stale Codex bindings in this preflight route, not a general permission to dissolve model locks or treat every skipped compaction as harmless.
The next signal is a shipped path
For an operator, the useful question is now precise: does the installed OpenClaw build contain this required-preflight route, and can a disposable Codex app-server session cross its context budget without discarding the next message? The evidence here is a public issue, PR, main-branch change, and focused tests—not a release receipt or a fleet reliability study. Watch for the version that carries the patch and for an independent end-to-end report; until then, “automatic compaction” is still a contract worth checking at the handoff.