$ 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
- → Apply the openclaw payment credential redaction commit to prevent credential leakage in logs openclaw/openclaw [immediate]
- → Review the new `openclaw proxy validate` command and adopt it in proxy preflight checks openclaw/openclaw [plan]
- → Enable `channels.bluebubbles.replyContextApiFallback` in config if you run BlueBubbles and need reliable reply context openclaw/openclaw [plan]
- → Monitor the auto-reply fix to group visible replies for delivery regressions openclaw/openclaw [monitor]
References
- [1] security(logging): redact payment credential fields (#75230) ↗ openclaw/openclaw
- [2] feat: add proxy validation command ↗ openclaw/openclaw
- [3] feat(bluebubbles): add reply-context API fallback for cache misses ↗ openclaw/openclaw
- [4] fix(auto-reply): keep group visible replies deliverable ↗ openclaw/openclaw
- [5] refactor: remove dead private helpers ↗ openclaw/openclaw
- [6] fix(security): harden report sanitizers ↗ openclaw/clownfish