43 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-05-31
stories 68

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Node bootstrap pairing completed, generated-media prompts clarified

By RepoJournal · Filed · About OpenClaw

OpenClaw fixed the Windows node bootstrap handoff and reshaped how generated media is delivered across session types.

The Windows node now completes its bootstrap handoff: a post-approval `hello-ok` can move the connection out of `PairingRequired`, and the node bootstrap handoff token is no longer stored as the operator `DeviceToken`, which previously caused an operator token mismatch on restart in a Crabbox alpha.13 repro [1]. The companion changes let node-mode startup proceed when an active gateway record still carries a bootstrap setup-code token [2], and make setup-code bootstrap clients pair as `node` first so the gateway can apply the native QR/setup bootstrap profile [3]. These land after the `v0.6.0-alpha.11` signed installer was verified on an Azure Windows desktop with a matching SHA-256 and valid Authenticode [3].

Generated media delivery guidance moved from a Discord skill into the shared system prompt: message-tool-only sessions are told to pass generated media as message-tool media/attachments, while automatic source delivery sessions should emit own-line `MEDIA` directives. Message-media compat aliases remain accepted at runtime but are hidden from the model-facing schema [4]. Separately, auth handling now treats inherited OAuth expiry comparisons as valid date timestamps rather than only finite numbers, and child-agent auth stores no longer persist inherited OAuth profiles whose local expiry is outside the supported JavaScript date range [5].

Steipete also landed a series of bounds and conversions across agents: OpenAI realtime secret expiry conversion [6], Nostr seen-tracker capacity bounding [7], and gateway health-monitor interval bounding [8]. The docs repo mirrored source changes four times [9][10][11][12] and improved its 404 page [13].

Action items

References

  1. [1] fix(pairing): complete node bootstrap handoff ↗ openclaw/openclaw-windows-node
  2. [2] fix(pairing): allow node bootstrap startup ↗ openclaw/openclaw-windows-node
  3. [3] fix(pairing): bootstrap setup codes as node first ↗ openclaw/openclaw-windows-node
  4. [4] fix: clarify generated media reply prompts ↗ openclaw/openclaw
  5. [5] fix(auth): bound inherited oauth expiry ↗ openclaw/openclaw
  6. [6] fix(openai): convert realtime secret expiry ↗ openclaw/openclaw
  7. [7] fix(nostr): bound seen tracker capacity ↗ openclaw/openclaw
  8. [8] fix(gateway): bound health monitor intervals ↗ openclaw/openclaw
  9. [9] chore(sync): mirror docs from openclaw/openclaw@005da57957c99111139b85aeceefd4f95b5801c5 ↗ openclaw/docs
  10. [10] chore(sync): mirror docs from openclaw/openclaw@961691def2e42f211243f6516bb8e0ac42de102a ↗ openclaw/docs
  11. [11] chore(sync): mirror docs from openclaw/openclaw@dcc329ac09eef51f24073e66b5b72762c0904fa2 ↗ openclaw/docs
  12. [12] chore(sync): mirror docs from openclaw/openclaw@99ce71ddbbdb93627605c01b7b9ac5e7c280afde ↗ openclaw/docs
  13. [13] fix: improve docs 404 page ↗ openclaw/docs

Quick answers

What shipped in OpenClaw on May 31, 2026?
OpenClaw fixed the Windows node bootstrap handoff and reshaped how generated media is delivered across session types. In total, 62 commits and 6 pull requests landed.
Who contributed to OpenClaw on May 31, 2026?
3 developers shipped this update, including steipete, vincentkoc, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
fix(pairing): complete node bootstrap handoff, fix(pairing): allow node bootstrap startup, and fix(pairing): bootstrap setup codes as node first.