OpenClaw: Closing the Message-Loss Window

Today's merges were dominated by a single reliability push — five separate messaging channels got durable ingress fixes to stop dropping messages across restarts and crashes — alongside a parallel effort to bring native macOS and Linux clients up to par with web chat.

Duration: PT2M36S

Episode overview

This episode is a short developer briefing from OpenClaw.

It explains recent repository work in plain language.

  • Show: OpenClaw
  • Published: 2026-07-18T06:04:10Z
  • Audio duration: PT2M36S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good evening. It's July 18th, and today's OpenClaw activity has one clear signal: message durability, everywhere.

Five channel integrations — Discord, iMessage, WhatsApp, Microsoft Teams, and Mattermost — all shipped fixes today tied to the same root issue, tracked under number 109657. The pattern was identical across all of them: a message arrives, the gateway crashes or restarts before it's fully dispatched, and the message…

Second theme: infrastructure hardening around the gateway itself. PR 110271 fixes a case where a schema mismatch after a downgrade caused a 21-gigabyte integrity scan to run repeatedly on the main thread, pinning CPU. PR 110323 makes gateway start and stop idempotent, so scripts and agents stop fighting over a…

Third theme: client parity. Multiple PRs — 110339, 110276, 110254, and 110285 — continue converging macOS, iOS, and Linux native clients toward the same model picker, copy behavior, and quick-chat features already in web chat, all built on shared OpenClawKit code.

Worth a mention: PR 110248 adds CI enforcement so script type declarations can't drift from their implementations again, closing the exact class of bug that caused three earlier repair PRs.

What'…

Nearby episodes from OpenClaw

  1. Local Models, Durable State, and a Very Busy Merge Queue
  2. Cleanup Sprint Meets Reliability Fixes
  3. The Great Untangling
  4. Onboarding Fixes and the Great Export Cleanup
  5. Weekly Recap - Durability, Cleanup, and Control UI Polish
  6. The Great Cleanup
  7. SQLite Hardening and the Fleet Grows Up
  8. Closing the Gaps on Approval Safety and Runtime Correctness