51 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-06-11
stories 174

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

ClickClack explicit enable, durable auto-reply summaries

By RepoJournal · Filed · About OpenClaw

ClickClack can now be explicitly enabled even with a nonempty plugin allowlist, and CLI-backed auto-reply runs now record durable tool summaries.

ClickClack now accepts an explicit enable/setup selection even when a nonempty plugin allowlist is configured, preserving unrelated allowlist rejections, denylist authority, and global plugin disablement [1]. Multi-bot Discord setups no longer silently miss command registration: the command-deploy cache is now scoped by application id, so a secondary account with the same command set won't be skipped by the shared cache [2].

Auto-reply tool activity is now durable in CLI-backed runs. The runner bridge previously dropped tool result events, so CLI runs had no durable tool record under verbose mode, while embedded runs did. Both runners now feed a summary tracker that renders the same formatToolAggregate line as the embedded runner [3]. Inter-tool commentary also becomes durable via the existing verbose standalone-progress path, using the `/verbose on` gate with no new config key, and works on every channel using the generic dispatch path [4].

Session model overrides survive daily/idle rollover. User-driven /model and sessions.patch overrides were dropped at the reset boundary because override preservation was gated on resetTriggered, missing implicit stale rollovers, the common case for always-on channel sessions [5].

Clownfish changed security job handling: live security-labeled jobs are now held, security routing stays item-scoped, and closed security hold jobs are finalized [6][7][8]. This appears to be a policy reversal (jobs that were previously released are now held again), so clusters processing security-labeled work may see jobs pause. Additionally, three container providers (parallels, proxmox, multipass) now properly remove lease/claim state after cleanup [9][10][11], and local-container gained native Docker checkpoint support via docker commit and checkpoint forks [12][13].

Docs mirrored the source changes across five commits from openclaw/openclaw [14][15][16][17][18], so documentation should reflect these changes.

Action items

References

  1. [1] fix(clickclack): allow explicit enable through plugin allowlist (#92084) ↗ openclaw/openclaw
  2. [2] fix(discord): scope command-deploy cache by application id ↗ openclaw/openclaw
  3. [3] feat(auto-reply): emit durable tool summaries from CLI runner tool results ↗ openclaw/openclaw
  4. [4] feat(auto-reply): durable inter-tool commentary via verbose standalone progress (supersedes #89850/#89890) ↗ openclaw/openclaw
  5. [5] fix(sessions): preserve user model override across daily/idle rollover (#90128) ↗ openclaw/openclaw
  6. [6] fix: hold live security-labeled jobs ↗ openclaw/clownfish
  7. [7] fix: keep security routing item-scoped ↗ openclaw/clownfish
  8. [8] chore: finalize closed security hold jobs ↗ openclaw/clownfish
  9. [9] fix(parallels): remove cleanup lease state ↗ openclaw/crabbox
  10. [10] fix(proxmox): remove claims after cleanup ↗ openclaw/crabbox
  11. [11] fix(multipass): remove claim after metadata rollback ↗ openclaw/crabbox
  12. [12] feat(local-container): add native checkpoint support via docker commit (#206) ↗ openclaw/crabbox
  13. [13] feat(local-container): add native checkpoint forks (#208) ↗ openclaw/crabbox
  14. [14] chore(sync): mirror docs from openclaw/openclaw@418d7e1e83c560c14139cd8c1e043b8f374a446c ↗ openclaw/docs
  15. [15] chore(sync): mirror docs from openclaw/openclaw@8e81bf774e30e09572407259201a953fca8cfc29 ↗ openclaw/docs
  16. [16] chore(sync): mirror docs from openclaw/openclaw@25ca39e87622b04f1f24ffddb0317481a2f13aa8 ↗ openclaw/docs
  17. [17] chore(sync): mirror docs from openclaw/openclaw@400b3e04fbda6667b97e932e426fa50615e3205a ↗ openclaw/docs
  18. [18] chore(sync): mirror docs from openclaw/openclaw@adad27d7448e5cf453451d8e2a136d6771728c58 ↗ openclaw/docs

Quick answers

What shipped in OpenClaw on June 11, 2026?
ClickClack can now be explicitly enabled even with a nonempty plugin allowlist, and CLI-backed auto-reply runs now record durable tool summaries. In total, 164 commits and 10 pull requests landed.
Who contributed to OpenClaw on June 11, 2026?
6 developers shipped this update, including Peter Steinberger, Cameron Beeley, Marvinthebored, lonexreb, Vincent Koc, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
fix(clickclack): allow explicit enable through plugin allowlist (#92084), fix(discord): scope command-deploy cache by application id, and feat(auto-reply): emit durable tool summaries from CLI runner tool results.