The workspace-boundary fix is on neither stable channel, and the one that moved this window still ships without it
The fix closes a symlink-then-parent-directory bypass in the sandbox path assertion. It merged to the default branch on 2026-07-27. Checked by ancestry against every non-prerelease tag, it is in none of them, and confirmed at file level: the published tarballs for both stable dist-tags contain neither of the functions the fix introduces, while the beta tarball does. The extended-stable line moved during this window, eight days after the fix merged, and moved without it, because that line diverged in June and later publishing on it cannot deliver the fix.
What this changes for operators
- Re-audit rather than upgrade-and-relax. Both stable channels are checkable in one command: neither published tarball contains the new path-resolution functions.
- Do not treat the sandbox path assertion as the barrier between an agent and the rest of the host on a stable channel. Keep agent workspaces on filesystems you would be willing to expose.
- Watch for the first non-prerelease tag on the 2026.8 line. That is the earliest point the fix can reach a stable channel.
Signal metadata
Source findings
- 2026-08-10-openclaw-openclaw-s-extended-stable-moved-to-2026-6-34-in-the-window-and-still 2026-08-10-openclaw-openclaw-s-extended-stable-moved-to-2026-6-34-in-the-window-and-still
Run: 2026-08-10-weekly-digest-2026-08-03_2026-08-10-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-08-10-openclaw-boundary-fix-on-no-stable-channel
Research evidence and publication history are open in the repository.