104 wires and counting

$ follow OpenClaw

Keep up with OpenClaw in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-03
stories 63

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Delayed chat commands no longer survive gateway reconnects

By RepoJournal · Filed · About OpenClaw

OpenClaw fixed a bug where delayed Control UI chat commands, including a queued /reset, could outlive the gateway connection and apply to a replacement session.

Delayed chat commands in the Control UI can no longer cross gateway reconnects. Commands held by session-state loading, reset confirmation, an active run, or durable queue delivery used to continue after a reconnect, so a queued `/reset` could apply to a replacement Gateway and the first send after `/clear` could retain a stale buffer. Commands are now cancelled when the connection, session selection, or authorization context changes [1]. A related commit also cancels chat scrolls on reconnect [2].

The system-agent setup path is faster. Verified inference setup repeatedly rediscovered process-stable plugin metadata across the baseline, staged, persisted, retried, and reconciled routes for each activation; it now prepares one compatibility-checked plugin manifest list after the setup plan and Codex install/registry refresh, then carries that immutable list through route selection [3]. The change is reflected in a release-owned changelog commit as well [4].

Test-only consolidation in the auto-reply suite removes 239 net lines. Repeated workspace-auth and nested-provider model fixtures are merged into a canonical directive parameter builder with a shared command runner, and the exec/verbose persistence policy matrix is compacted while preserving every named case and outcome. Production code is untouched [5].

Docs received five routine sync mirrors from openclaw/openclaw; no content changes of note [6][7][8][9][10].

Action items

References

  1. [1] fix: stop delayed chat commands crossing gateway reconnects ↗ openclaw/openclaw
  2. [2] fix: cancel chat scrolls on reconnect ↗ openclaw/openclaw
  3. [3] perf(system-agent): reuse setup metadata per activation ↗ openclaw/openclaw
  4. [4] perf(system-agent): reuse setup metadata per activation (#118352) ↗ openclaw/openclaw
  5. [5] test(auto-reply): consolidate model directive fixtures ↗ openclaw/openclaw
  6. [6] chore(sync): mirror docs from openclaw/openclaw@e04caa6aee3844f7dc4772e6c350401edd811aa3 ↗ openclaw/docs
  7. [7] chore(sync): mirror docs from openclaw/openclaw@d985d771d987739617f550a1510812ead43f87e5 ↗ openclaw/docs
  8. [8] chore(sync): mirror docs from openclaw/openclaw@d7def97638c3a265f07e4fa23bf806c0778741e6 ↗ openclaw/docs
  9. [9] chore(sync): mirror docs from openclaw/openclaw@b0e023a241dcc7af3d7a408d3647dab30f716961 ↗ openclaw/docs
  10. [10] chore(sync): mirror docs from openclaw/openclaw@b438b9605f336e060b2c9695b2c672378e4da34b ↗ openclaw/docs

Quick answers

What shipped in OpenClaw on August 3, 2026?
OpenClaw fixed a bug where delayed Control UI chat commands, including a queued /reset, could outlive the gateway connection and apply to a replacement session. In total, 58 commits and 5 pull requests landed.
Who contributed to OpenClaw on August 3, 2026?
3 developers shipped this update, including steipete, shakkernerd, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
fix: stop delayed chat commands crossing gateway reconnects, fix: cancel chat scrolls on reconnect, and perf(system-agent): reuse setup metadata per activation.