77 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-12
stories 239

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Fail-closed task registry, real Google Meet leaves

By RepoJournal · Filed · About OpenClaw

openclaw now fails closed on task registry restore errors instead of silently losing durable state, and the Google Meet transport actually leaves the call when told to.

A task-registry SQLite restore error used to be logged and then treated as an empty registry, so reads could silently report missing tasks and later writes could overwrite or prune durable task state that had failed to load. Clawsweeper now fails closed on restore failure and keeps the gateway process alive on in-process restart, preserving the failure for task delivery paths instead of hiding it [1].

The `openclaw googlemeet leave` command on Chrome transports printed `left <session-id>` and marked the session ended, but only ran the registered stop hook; the browser participant kept sitting in the call as a ghost receiving audio or captions. It now actually leaves the Meet call in the browser [2].

Clawsweeper added new close policies targeting old backlog: a default-off issue-only `unsponsored_feature_request` close reason for 90-day-old issues with sponsorship, activity, popularity, linked-PR, and security gates, and widened `stale_insufficient_info` to materially outdated reports with a 60-day non-bot comment inactivity guard [3]. In Clownfish, the autonomous cleanup wave is now restricted: security-adjacent PRs are excluded and only low-risk merges are allowed [5]. Native locale artifact handling was hardened to keep source and per-locale artifacts exact when Swift or Kotlin UI copy moves into helper calls, conditional branches, or typed fallback expressions [4].

Action items

References

  1. [1] fix(tasks): fail closed when task registry restore fails ↗ openclaw/openclaw
  2. [2] fix(google-meet): actually leave the Meet call in the browser on leave (#103386) ↗ openclaw/openclaw
  3. [3] feat: expand close policies for old backlog ↗ openclaw/clawsweeper
  4. [4] fix(i18n): keep native locale artifacts exact ↗ openclaw/openclaw
  5. [5] chore(queue): add fresh autonomous cleanup wave (#306) ↗ openclaw/clownfish

Quick answers

What shipped in OpenClaw on July 12, 2026?
openclaw now fails closed on task registry restore errors instead of silently losing durable state, and the Google Meet transport actually leaves the call when told to. In total, 206 commits and 33 pull requests landed.
Who contributed to OpenClaw on July 12, 2026?
4 developers shipped this update, including Peter Steinberger, Vincent Koc, lonexreb, and vyctorbrzezowski.
What were the notable OpenClaw updates?
fix(tasks): fail closed when task registry restore fails, fix(google-meet): actually leave the Meet call in the browser on leave (#103386), and feat: expand close policies for old backlog.