OpenClaw v2026.3.2-beta.1: Secrets/SecretRef coverage, boundary review

The security lens for v2026.3.2-beta.1 is its trust boundary. The official record describes an access, approval, or trust-boundary change; this reading keeps the exact tag visible and turns the source bullets into checks an operator can actually repeat.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Boundary review

Secrets/SecretRef coverage

What changed. expand SecretRef support across the full supported user-supplied credential surface (64 targets total), including runtime collectors, openclaw secrets planning/apply/audit flows, onboarding SecretInput UX, and related docs; unresolved refs now fail fast on active surfaces while inactive surfaces report non-blocking diagnostics.

Check it with. The useful evidence for Secrets/SecretRef coverage is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Tools/PDF analysis

What changed. add a first-class pdf tool with native Anthropic and Google PDF provider support, extraction fallback for non-native models, configurable defaults (agents.defaults.pdfModel, pdfMaxBytesMb, pdfMaxPages), and docs/tests covering routing, validation, and registration.

Check it with. For Tools/PDF analysis, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

Outbound adapters/plugins

What changed. add shared sendPayload support across direct-text-media, Discord, Slack, WhatsApp, Zalo, and Zalouser with multi-media iteration and chunk-aware text fallback.

Check it with. Use Outbound adapters/plugins as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

Plugin command/runtime hardening

What changed. validate and normalize plugin command name/description at registration boundaries, and guard Telegram native menu normalization paths so malformed plugin command specs cannot crash startup (trim on undefined). Fixes #31944.

Check it with. Use Plugin command/runtime hardening as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

What the implementation list adds

Telegram

guard duplicate-token checks and gateway startup token normalization when account tokens are missing, preventing token.trim() crashes during status/start flows.

Telegram lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Secrets/SecretRef coverage.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
4. Compare the transcript before and after reconnect, including delivery state and any visible error.
5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Plugin command/runtime hardening. validate and normalize plugin command name/description at registration boundaries, and guard Telegram native menu normalization paths so malformed plugin command specs cannot crash startup (trim on undefined). Fixes #31944. Keep the reproduction and the post-fix result together in the acceptance record.

Telegram. guard duplicate-token checks and gateway startup token normalization when account tokens are missing, preventing token.trim() crashes during status/start flows. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.3.2-beta.1 release notes for the exact change list, then cross-check the official release index and the Gateway security guide before acting.