106 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-08-05
stories 50

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Gateway drain-loop deadlock fixed, QA lease leaks closed

By RepoJournal · Filed · About OpenClaw

OpenClaw fixed a zero-work drain loop in the auto-reply gateway and plugged QA lease leaks, both caused by recent policy changes.

The auto-reply gateway could stall in a zero-work drain loop after a queue drop policy change, blocking all outgoing messages. The fix preserves pending overflow summaries, records queue cap outcomes, and aligns summary lines with sources, ensuring the gateway drains correctly and no work is lost [1].

QA runs had two leak paths: isolated runs could permanently leak a channel credential lease after one transient cleanup failure, and runtime-parity runs could leave their owned lab server running while hiding the original scenario failure. The isolated-suite owner now records transport cleanup only after success, preserving the registry retry contract; the runtime-parity owner uses canonical cleanup aggregation so every owned lab stops [2].

Continuing the project-wide production LOC reduction, Telegram outbound actions, edits, forum topics, and rich-message handling now share canonical option contracts and target parsing without changing the plugin public surface [3]. Related consolidation in infra unifies platform/service path and usage rollup owners while preserving Nix/workspace ordering and all accounting [4].

Channel preview streaming now respects explicit `streaming.mode: partial` over inherited defaults in Telegram and Discord. Precedence is centralized in `src/channels/streaming.ts`: explicit channel block setting wins over eligible explicit preview modes, and the reply runner classifies item events for CLI preamble capture without leaking hidden commentary into final answers [5].

Action items

References

  1. [1] fix: auto-reply gateway stalls in a zero-work drain loop after a queue drop policy change (#119331) ↗ openclaw/openclaw
  2. [2] fix(qa): release failed transport leases and always stop owned labs ↗ openclaw/openclaw
  3. [3] refactor(telegram): consolidate outbound contracts and targets ↗ openclaw/openclaw
  4. [4] refactor(infra): consolidate service paths and usage rollups ↗ openclaw/openclaw
  5. [5] fix(channels): keep preview streaming quiet and non-blocking ↗ openclaw/openclaw

Quick answers

What shipped in OpenClaw on August 5, 2026?
OpenClaw fixed a zero-work drain loop in the auto-reply gateway and plugged QA lease leaks, both caused by recent policy changes. In total, 25 commits and 25 pull requests landed.
Who contributed to OpenClaw on August 5, 2026?
3 developers shipped this update, including ml12580, steipete, and SYU8384.
What were the notable OpenClaw updates?
fix: auto-reply gateway stalls in a zero-work drain loop after a queue drop policy change (#119331), fix(qa): release failed transport leases and always stop owned labs, and refactor(telegram): consolidate outbound contracts and targets.