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-30
stories 104

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Extracting LLM core, surfacing chat errors, hardening Windows bootstrap

By RepoJournal · Filed · About OpenClaw

OpenClaw extracts shared LLM contracts into new packages while the Windows gateway gets hardened reconnects and visible chat error messages.

OpenClaw split shared LLM functionality out of the monolith into `packages/llm-core` and `packages/llm-runtime` [1]. Existing entrypoints like `src/llm/*` and `packages/agent-core/src/llm.ts` remain as compatibility facades, so consumers should see no breakage, but the new tsdown builds add declared dist exports for the packages [1]. This is a preparatory refactor, not a behavior change.

Chat errors in the Control UI will now surface as visible assistant messages instead of failing silently [2]. The gateway emits error events as assistant messages, and the UI renders active-run errors while avoiding duplicate or orphan bubbles after failed sends. Regression coverage was added for both server-provided and synthesized error messages [2].

The Windows node bootstrap pairing was hardened against gateway auth compatibility failures seen during Crabbox release validation [3]. Fresh bootstrap handshakes now start with v2 signatures, a gateway-level `RequiresV2Signature` flag persists after v2 fallback for reconnects, and stale operator device tokens are recovered on `AUTH_DEVICE_TOKEN_MISMATCH` [3]. The Windows installer now gives users an explicit choice to remove the local WSL `OpenClawGateway` during uninstall, with silent uninstalls still removing it automatically [5]. Also, the release now bundles x64 VC runtime DLLs and verifies native dependencies, though ARM64 portable ZIP is paused [6].

Crabbox added ARM Linux lease architecture selection with `--arch` for Azure and AWS, routing ARM64 to Azure Dpsv6/Dpdsv6 and AWS Graviton families [4]. This includes resolving matching Ubuntu ARM64 images and keeping AWS promoted-image lookups architecture-scoped [4]. Broker cost cap defaults were enabled for the Worker deploy config [7].

Action items

References

  1. [1] refactor: extract LLM core packages ↗ openclaw/openclaw
  2. [2] fix: show chat errors as visible messages ↗ openclaw/openclaw
  3. [3] fix(pairing): harden Windows node bootstrap reconnects ↗ openclaw/openclaw-windows-node
  4. [4] feat: add ARM Linux lease architecture selection ↗ openclaw/crabbox
  5. [5] Add uninstall choice for local WSL gateway ↗ openclaw/openclaw-windows-node
  6. [6] fix(release): bundle VC runtime dependencies ↗ openclaw/openclaw-windows-node
  7. [7] fix: enable broker cost cap defaults ↗ openclaw/crabbox

Quick answers

What shipped in OpenClaw on May 30, 2026?
OpenClaw extracts shared LLM contracts into new packages while the Windows gateway gets hardened reconnects and visible chat error messages. In total, 88 commits and 16 pull requests landed.
Who contributed to OpenClaw on May 30, 2026?
8 developers shipped this update, including steipete, adele-with-a-b, Ayaan Zaidi, Scott Hanselman, paulcam206, vincentkoc, ranjeshj, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
refactor: extract LLM core packages, fix: show chat errors as visible messages, and fix(pairing): harden Windows node bootstrap reconnects.