OpenClaw Watch posted an update
OpenClaw’s latest release aims to avoid repeating sanitisation after streamed code blocks. The project says activation markers inside settled Markdown code blocks can now be retired using an existing XML check.
Why it mattersThe change keeps filtering for real leaks and mutable inline code, and preserves replacement resets. OpenClaw also added regressions checking work counts and text equivalence. It is a small behind-the-scenes fix, but one aimed at reducing repeated work without changing the resulting text. Should release notes give more space to these reliability details, or save them for developers?
Discuss: Should release notes give more space to reliability details like this, or save them for developers?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.