Evidence record / openclaw
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-openclaw-the-codex-sandbox-stop-success-fix-and-the-rest-of-the-parent-s-main-only-pile-reached-the
The Codex sandbox stop-success fix and the rest of the parent’s main-only pile reached the same tags. The fix touches extensions/codex/src/app-server/sandbox-exec-server/* (commit file list): it reaps the process tree before reporting termination. It ships in the @openclaw/codex plugin published in lockstep at each version. The capability items from the parent (per-session read-only/guarded/workspace/full modes, forge credential kept on the Gateway) are installable on stable from 2026-08-31.
Channel: tagged-release (not in extended-stable). Half: both. Date: 2026-08-24 / 2026-08-31.
Operator consequence: On 2026.8.1+ a successful Codex sandbox stop means the tree is gone. Before 8.1, and on extended-stable, it did not. Operators can now plan around “cloud worker finishes, Gateway opens the draft PR, worker never holds the token”.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-openclaw-the-codex-sandbox-stop-success-fix-and-the-rest-of-the-parent-s-main-only-pile-reached-the
Profile citations
- OpenClaw / claim / sandbox-stop-fix-stable
Source links
Primary links, including exact changelog lines when available.
- commit2026-09-21-openclaw-the-codex-sandbox-stop-success-fix-and-the-rest-of-the-parent-s-main-only-pile-reached-thegithub.com/openclaw/openclaw/commit/fd8326c5bf6fcf063fd1ac0d9e87bf032fbfa2dcgithub release2026-09-21-openclaw-the-codex-sandbox-stop-success-fix-and-the-rest-of-the-parent-s-main-only-pile-reached-theopenclaw/openclaw / v2026.8.1
Versioned source: run artifact