121 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-25
stories 98

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Automation provenance fix, CLI session bindings preserved

By RepoJournal · Filed · About OpenClaw

OpenClaw now records the creator of person-created automations in activity, and CLI conversations survive non-expiry failures.

OpenClaw fixes activity attribution for person-created automations: sessions started this way now carry the creator's canonical profile ID as private cron-job provenance, so they appear under the creator in Activity and its people filter [1]. Separately, valid persisted CLI and Agent SDK conversation bindings are no longer discarded on failures that don't prove the provider session expired; only `FailoverError(reason === "session_expired")` does, and the fresh-recovery policy in `CliBackendConfig.freshSessionRecovery` now preserves existing bindings for undefined or `replace-binding` [2]. With these changes, activity histories are accurate and multi-turn CLI conversations are more reliable.

Three fixes reduce operational blind spots. Verbose health and deep status commands no longer hit a global Gateway transport timeout when one channel probe stalls; the Gateway now owns a fixed live-health deadline below the tightest first-party client budget, keeping healthy sibling channels visible [3]. In Crabbox, retained AWS lease runs can now request durable run-session handles with `--lease-output`, aligning AWS with the provider-neutral run-session contract [4], and `inspect` now exposes coordinator cleanup state in shared structured status views, distinguishing confirmed deletion, pending cleanup, failure, retry, or intentional retention [5].

Codex runtime management moves to app-server 0.149.1 on OpenClaw `main`, closing the gap with 0.149.x custom runtimes that could reach incompatible protocol boundaries [6]. The Crabbox Live activity UI compacts its filters so the Tool selector collapses, and search, primary status controls, and Auto-follow stay visible [7]. Crabbox also adds opt-in `sync.gitOverlay` for Linux SSH-backed workspaces, preparing runners from the exact advertised Git commit with complete filtered history [8], and reduces provisioning read pressure on Machine0 so warm-ups can exhaust the hourly API read quota less easily [9].

The docs were synced five times from openclaw/openclaw commits [10][11][12][13][14]. One previously proposed typed ready-pool identity matching change remains pending, but it was not merged; no action is needed there. Most of these changes are aimed at stabilization, so plan to test them in staging first, especially if you rely on CLI session continuity or verbose health diagnostics.

Action items

References

  1. [1] fix: automation runs appear in creator activity ↗ openclaw/openclaw
  2. [2] fix(agents): preserve valid CLI session bindings ↗ openclaw/openclaw
  3. [3] fix: keep verbose health available when channel probes stall ↗ openclaw/openclaw
  4. [4] fix(aws): allow retained runs to emit session handles ↗ openclaw/crabbox
  5. [5] fix(inspect): expose coordinator cleanup state ↗ openclaw/crabbox
  6. [6] feat(codex): upgrade main to app-server 0.149.1 ↗ openclaw/openclaw
  7. [7] improve(ui): compact Live activity filters ↗ openclaw/openclaw
  8. [8] feat: add opt-in Git overlay sync ↗ openclaw/crabbox
  9. [9] fix(machine0): reduce provisioning read pressure ↗ openclaw/crabbox
  10. [10] chore(sync): mirror docs from openclaw/openclaw@e9017714c2d64cb564b467648d8a5c36dd191bff ↗ openclaw/docs
  11. [11] chore(sync): mirror docs from openclaw/openclaw@b68c136609049e65852cb400052fec65539f066a ↗ openclaw/docs
  12. [12] chore(sync): mirror docs from openclaw/openclaw@2d7b1d21d3527b2f218f3d49dcf888622c38e67a ↗ openclaw/docs
  13. [13] chore(sync): mirror docs from openclaw/openclaw@2e9c8f8d3f21bc91e44ac102e68191cf09cc339a ↗ openclaw/docs
  14. [14] chore(sync): mirror docs from openclaw/openclaw@e27433c22ed7a2ca419ae0c6c506933da699a4e7 ↗ openclaw/docs

Quick answers

What shipped in OpenClaw on August 25, 2026?
OpenClaw now records the creator of person-created automations in activity, and CLI conversations survive non-expiry failures. In total, 63 commits and 35 pull requests landed.
Who contributed to OpenClaw on August 25, 2026?
6 developers shipped this update, including roboclaw-bot, SunnyShu0925, steipete, clawsweeper, vincentkoc, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
fix: automation runs appear in creator activity, fix(agents): preserve valid CLI session bindings, and fix: keep verbose health available when channel probes stall.