RepoJournal
OpenClaw @openclaw
45 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-10
stories 136
GitHub RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Gateways: v3 signing fixes connection, mDNS UI removed

By RepoJournal · Filed · About OpenClaw

Ranjesh Jaganathan Peter Steinberger Vincent Koc openclaw-docs-sync[bot]
4 people shipped this
Ranjesh Jaganathan @ranjeshj 5 cited Peter Steinberger @steipete 3 cited Vincent Koc @vincentkoc 1 cited openclaw-docs-sync[bot] @openclaw-docs-sync[bot]

The Windows node now speaks v3 signaling exclusively, fixing the most disruptive connection failures and removing the now-dead discovery UI.

The connection protocol in the Windows node now matches the reference implementation. The client uses SignConnectPayloadV3 instead of the legacy SignPayload/BuildDebugPayload, and the operator-4-mode signature cascade (V3Auth→V3Empty→V2Auth→V2Empty) is gone. "Signature rejection = real" means failures now surface as genuine errors instead of falling back to older auth modes [1]. This is a breaking change for any gateway that still expects v2 signatures.

The ConnectionPage UX was rebuilt, borrowing from node-2: a status card with a disconnect button and connection attempts counter, live decode preview for setup codes via manager.ApplySetupCodeAsync(), and a Recent Gateways card listing GatewayRegistry entries with connect/remove actions [2]. Available Gateways discovery is gone, along with the mDNS scan button and related code-behind (AutoScanAsync, PopulateGatewayList, OnConnectToGateway, OnConnectWithToken, OnCancelTokenPrompt). Gateway switching now flows through GatewayRegistry [3]. Pairing state no longer gets overwritten by disconnect events, so after the gateway sends PAIRING_REQUIRED and closes the socket, the UI stays on the Pairing screen [4].

The architecture wiring is also further along: SettingsChangeImpact classifier prevents reconnects for UI-only changes, DeviceIdentityStore persists tokens, SshTunnelManager.StartAsync is no longer a stub, and NodeConnector starts after operator handshake [5]. In openclaw, housekeeping removed the legacy cmd installer [6] and cleaned BlueBubbles references [7]. A new Telegram mantis evidence builder is in development [8], and auth default models were canonicalized [9].

Action items

References

  1. [1] Fix connection protocol: v3 signatures, remove cascade, structured errors ↗ openclaw/openclaw-windows-node
  2. [2] Upgrade ConnectionPage UX with manager integration ↗ openclaw/openclaw-windows-node
  3. [3] Remove Available Gateways discovery section from ConnectionPage ↗ openclaw/openclaw-windows-node
  4. [4] Fix pairing state: don't let disconnect overwrite PairingRequired ↗ openclaw/openclaw-windows-node
  5. [5] Wire connection architecture: settings classifier, identity store, node connector, per-gateway identity ↗ openclaw/openclaw-windows-node
  6. [6] chore(installer): remove legacy cmd installer ↗ openclaw/openclaw
  7. [7] chore(channels): remove bluebubbles hangover ↗ openclaw/openclaw
  8. [8] feat: add telegram mantis evidence builder ↗ openclaw/openclaw
  9. [9] fix(models): canonicalize auth default models ↗ openclaw/openclaw
Topics: AI Agents AI / ML Full archive →

Quick answers

What shipped in OpenClaw on May 10, 2026?
The Windows node now speaks v3 signaling exclusively, fixing the most disruptive connection failures and removing the now-dead discovery UI. In total, 133 commits and 3 pull requests landed.
Who contributed to OpenClaw on May 10, 2026?
4 developers shipped this update, including Ranjesh Jaganathan, Peter Steinberger, Vincent Koc, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
Fix connection protocol: v3 signatures, remove cascade, structured errors, Upgrade ConnectionPage UX with manager integration, and Remove Available Gateways discovery section from ConnectionPage.
♥

$ log @openclaw --recent

Gesture update rollback guard fixed; Slack slackens redundant work 150 shipped Apple container inspect parsing hardened, QA scenarios move to YAML 108 shipped Copilot replay thinking blocks stripped, WhatsApp login persistence fixed 160 shipped Gateway mirrors commentary events, docs builder reusable for ClawHub 88 shipped

$ log --all # elsewhere on the wire

Meta React Native adds Stable API guards to renderer attributed string FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.