93 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-28
stories 68

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Healthy accounts keep actions despite failed credential

By RepoJournal · Filed · About OpenClaw

One credential failure no longer disables message actions for healthy accounts.

A fix in openclaw/openclaw ensures that a single failing credential SecretRef keeps unrelated healthy accounts usable, addressing the previously broad outage [1]. The change isolates unavailable account discovery so message actions for healthy accounts remain functional.

Crabbox injects reserved execution metadata (CRABBOX_LEASE_ID, CRABBOX_RUN_ID, CRABBOX_SLUG) authoritatively over ambient values [2], and pool capacity is now reconciled to desired ready counts [3].

Crabbox also refreshed dependencies, moving toolchain to Go 1.26.5 and removing five high-severity npm audit findings [4], and fixed Blaxel provider issues against current APIs [5].

Quick answers

What shipped in OpenClaw on July 28, 2026?
One credential failure no longer disables message actions for healthy accounts. In total, 37 commits and 31 pull requests landed.
Who contributed to OpenClaw on July 28, 2026?
6 developers shipped this update, including openclaw-docs-sync[bot], wangmiao0668000666, Peter Steinberger, masatohoshino, SebTardif, and arcabotai.
What were the notable OpenClaw updates?
fix(channels): keep healthy accounts' message actions when one credential SecretRef fails (#110329), feat: inject reserved execution metadata, and feat(pool): reconcile desired ready capacity.