Approved exec could run different bytes than the ones you approved
The bytes presented for approval and the bytes executed could differ. This is the same defect class the previous window recorded in a different product, which is why it is a signal here rather than a line in a provider note: two unrelated harnesses, two weeks apart, both shipped a version where the approval dialog was not a description of the action.
What this changes for operators
- The fix is on the default branch and in no release. State that plainly to anyone relying on the approval prompt in a stable install.
- When the same defect class appears in two unrelated codebases inside a fortnight, treat it as a property of the pattern rather than of the vendor. If you build approval UI, the invariant to test is that the string displayed and the string executed are the same object, not two renderings of one intention.
Primary sources
Signal metadata
Source findings
- 2026-08-17-openclaw-approved-exec-could-run-different-bytes-than-the-ones-you 2026-08-17-openclaw-approved-exec-could-run-different-bytes-than-the-ones-you
Run: 2026-08-17-weekly-digest-2026-08-10_2026-08-17-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-08-17-openclaw-approved-exec-ran-different-bytes
Research evidence and publication history are open in the repository.