Who contributed to OpenClaw on August 18, 2026?

4 developers shipped this update, including Peter Steinberger, Vyctor H. Brzezowski, SebTardif, and openclaw-docs-sync[bot].

What were the notable OpenClaw updates?

fix(browser): keep screenshot sharing hints capability-neutral (#125597), fix(ssh): persist static heartbeat lifecycle (#1381), and fix(aws): resume partial image deletion.

Aug 18, 2026

$ the-wire · showcase

Browser screenshot hints stop naming removed tools

By RepoJournal · Filed 19:50 UTC on September 7, 2026 · About OpenClaw

4 people shipped this

Peter Steinberger @steipete 3 cited

Vyctor H. Brzezowski @vyctorbrzezowski 2 cited

SebTardif @SebTardif 2 cited

openclaw-docs-sync[bot] @openclaw-docs-sync[bot]

OpenClaw fixed a browser bug where screenshot results could name a message tool that policy had removed, risking AI hallucinations.

The browser screenshot results in OpenClaw no longer name the message tool when policy has removed it from the model's effective tool surface [1]. The result now reports the staged sanitized outbound copy and its path without referencing an independently gated tool, so the output stays actionable without becoming hallucination bait. Tests for vision, fallback, and raw-image results now protect this contract.

Crabbox hardened provider lifecycle handling across SSH and cloud operations [2][3]. Static SSH heartbeat labels and explicit idle-timeout replacements are now persisted through exact claim compare-and-swap updates, with committed lifecycle state restored for fresh processes instead of synthesizing defaults. AWS image deletion resumes partial cleanup from a durable claim: it persists the image-deletion claim before AMI deregistration, then retries cleanup when AMIs or snapshots are already missing. Both changes close gaps where interrupted operations could leave leases or cloud resources in an inconsistent state.

Two related fixes address stalled data-plane endpoints hanging provider calls [4][5]. With Runtime.HTTP unset, fallback HTTP clients now separate lifecycle JSON calls from long-running uploads and streams, so a stalled lifecycle endpoint no longer hangs forever while data-plane work is bounded appropriately. The original proposal of a blanket 60-second timeout would have cut off valid long uploads; the rewrite splits ownership instead.

UI polish in the transcript removes the distraction of typing indicators outside the composer area [6]. Typing activity now participates in chronological transcript scrolling, and new interactions for Markdown tables let users copy tabular data or inspect wide tables without page-level horizontal scrolling [7].

Action items

→ Review and deploy the browser screenshot fix to prevent tool-name hallucinations in filtered tool surfaces openclaw/openclaw [plan]
→ Audit your SSH static lease handling for consistency with the new compare-and-swap lifecycle persistence openclaw/crabbox [monitor]
→ Verify your AWS image deletion works when partial cleanup is needed after a crash openclaw/crabbox [monitor]
→ Check whether your Runtime.HTTP setup has separate clients for lifecycle and data-plane calls to avoid hangs openclaw/crabbox [plan]

References

[1] fix(browser): keep screenshot sharing hints capability-neutral (#125597) ↗ openclaw/openclaw
[2] fix(ssh): persist static heartbeat lifecycle (#1381) ↗ openclaw/crabbox
[3] fix(aws): resume partial image deletion ↗ openclaw/crabbox
[4] fix(e2b): stalled API host can hang sandbox create and inspect ↗ openclaw/crabbox
[5] fix(http): stalled control plane can hang remaining providers ↗ openclaw/crabbox
[6] fix(ui): show users typing in the transcript ↗ openclaw/openclaw
[7] feat(ui): add Markdown table interactions ↗ openclaw/openclaw