The approved-exec fix is still in no release
Merge ab5611f0 (2026-08-17) binds exec approvals to the bytes that will run. The newest tag is still v2026.8.1-beta.2 from 2026-08-15. Compare that tag to the commit is ahead_by 619. This window cut zero OpenClaw releases.
What this changes for operators
- A tagged install still can run different bytes than the ones you approved. Say that to anyone relying on the prompt.
- Evidence that would settle: any tag where ab5611f0 is an ancestor.
Primary sources
Signal metadata
Source findings
- 2026-08-20-openclaw-approved-exec-fix-still-in-no-release 2026-08-20-openclaw-approved-exec-fix-still-in-no-release
Featured in
- The Classifier Is Off / 2026-08-20
Run: 2026-08-20-brief-2026-08-17_2026-08-20-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-08-20-openclaw-approved-exec-still-unreleased
Research evidence and publication history are open in the repository.