84 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-07-18
stories 89

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Gateway drain race fix, Tailscale Serve for WSL, setup fails closed

By RepoJournal · Filed · About OpenClaw

A fix for launchd reload ensures the gateway won't strand when restarts race the 300s drain window, while Windows now supports Tailscale Serve for private remote access.

The launchd reload handoff in openclaw now waits out the gateway's drain window before re-bootstrapping, closing a race where a restart could leave the gateway unavailable. Previously the handoff waited only ~3s, but the booted-out gateway keeps its label registered until drain completes (up to 300s), so bootstrap failed with EIO and the kickstart -k fallback couldn't recover. This is a fix for deployments that use launchd-driven gateway restarts. [1]

Concurrent managed updates are now single-flight at their shared infrastructure owner. Automatic update callers may join the active handoff, but only its owner schedules the Gateway restart and persists the restart intent, preventing multiple updater processes from racing service restart and state migration. This keeps the Gateway healthy under concurrent update triggers. [2]

Windows users with Tailscale get opt-in Tailscale Serve provisioning for WSL gateways. Generated WSL gateways were loopback-only, so Companion couldn't use a private tailnet endpoint. This adds browser/auth-key authorization, WSS gateway registration, and Tailscale-aware recovery, enabling secure remote access without LAN exposure. Separately, SetupEngine now fails closed when given invalid explicit configuration or malformed arguments, instead of silently falling back to bundled defaults. For example, `--config --headless` previously treated `--headless` as the config file path. [3][4]

ClawSweeper's OpenClaw Bay dashboard exposes exact-review pressure telemetry, and automerge worker health is consolidated into the Worker Health section. The refactor reorganizes dashboard presentation without changing telemetry collection or the API payload. [5][6]

Action items

References

  1. [1] fix: launchd reload handoff strands gateway when restart races the drain window (#110213) ↗ openclaw/openclaw
  2. [2] fix(update): keep gateway healthy during concurrent updates ↗ openclaw/openclaw
  3. [3] Add Tailscale Serve support for WSL gateways ↗ openclaw/openclaw-windows-node
  4. [4] fix: setup fails closed for invalid configuration arguments ↗ openclaw/openclaw-windows-node
  5. [5] feat(dashboard): OpenClaw Bay improvements (#597) ↗ openclaw/clawsweeper
  6. [6] Consolidate automerge worker health (#648) ↗ openclaw/clawsweeper

Quick answers

What shipped in OpenClaw on July 18, 2026?
A fix for launchd reload ensures the gateway won't strand when restarts race the 300s drain window, while Windows now supports Tailscale Serve for private remote access. In total, 57 commits and 32 pull requests landed.
Who contributed to OpenClaw on July 18, 2026?
9 developers shipped this update, including MatthewSynthia, Peter Steinberger, DaigoSoup, xialonglee, Barbara Kudiess, andyeskridge, calebeden, and brokemac79, and 1 more.
What were the notable OpenClaw updates?
fix: launchd reload handoff strands gateway when restart races the drain window (#110213), fix(update): keep gateway healthy during concurrent updates, and Add Tailscale Serve support for WSL gateways.