43 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-05-01
stories 141

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Payment credential redaction, proxy validation, and reply-context fallback land in openclaw

By RepoJournal · Filed · About OpenClaw

openclaw shipped a security patch that redacts payment credentials from logs, plus a proxy preflight command and an opt-in BlueBubbles reply-context fallback.

openclaw now redacts payment credential fields in structured logs and tool payload sanitization, driven by a key-aware redaction helper [1]. The change ships with updated tests and logging docs, closing a gap where sensitive fields could leak into logs.

Operators get `openclaw proxy validate` for preflight proxy checks, validating allowed and denied destinations with CLI output [2]. Maintainers required follow-ups before landing: custom allowed URLs are validated before probing, and proxy URL userinfo, query strings, and fragments are redacted from validation output, so no credentials leak during checks.

BlueBubbles channels gain an opt-in fallback for reply-context cache misses [3]. Off by default (`channels.bluebubbles.replyContextApiFallback: false`), it fetches the original message via `GET /api/v1/message/{id}` only when `replyToBody`/`replyToSender` are absent and the cache misses, amortizing context across subsequent replies; cache hits incur zero additional cost.

A fix keeps group visible replies deliverable by preserving the `message` tool and including group and subagent tool policy in fallback detection, so restricted rooms fall back to automatic delivery instead of going silent [4]. Separately, dead private helpers were removed [5], and clownfish hardened report sanitizers [6].

Action items

References

  1. [1] security(logging): redact payment credential fields (#75230) ↗ openclaw/openclaw
  2. [2] feat: add proxy validation command ↗ openclaw/openclaw
  3. [3] feat(bluebubbles): add reply-context API fallback for cache misses ↗ openclaw/openclaw
  4. [4] fix(auto-reply): keep group visible replies deliverable ↗ openclaw/openclaw
  5. [5] refactor: remove dead private helpers ↗ openclaw/openclaw
  6. [6] fix(security): harden report sanitizers ↗ openclaw/clownfish

Quick answers

What shipped in OpenClaw on May 1, 2026?
openclaw shipped a security patch that redacts payment credentials from logs, plus a proxy preflight command and an opt-in BlueBubbles reply-context fallback. In total, 126 commits and 15 pull requests landed.
Who contributed to OpenClaw on May 1, 2026?
6 developers shipped this update, including stain lu, Jesse Merhi, Peter Steinberger, coletebou, Vincent Koc, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
security(logging): redact payment credential fields (#75230), feat: add proxy validation command, and feat(bluebubbles): add reply-context API fallback for cache misses.