OpenClaw v2026.4.29-beta.2: Memory grows into a people-aware wiki with provenance, upgrade notes

v2026.4.29-beta.2 arrived on 2026-04-30 with a change that matters during maintenance: memory grows into a people-aware wiki with provenance. The page is a researched reading note from the official release record, with a test path for a real Gateway.

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.

Before the package changes

Messaging and automation get active-run steering by

What changed. Messaging and automation get active-run steering by default, visible-reply enforcement, spawned subagent routing metadata, and opt-in follow-up commitments for heartbeat-delivered reminders.

Check it with. For Messaging and automation get active-run steering by, 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.

Memory grows into a people-aware wiki with provenance

What changed. Memory grows into a people-aware wiki with provenance views, per-conversation Active Memory filters, partial recall on timeout, and bounded REM preview diagnostics.

Check it with. Measure Memory grows into a people-aware wiki with provenance after a fresh session and after a reconnect. The record should say what was retained, what was intentionally absent, and which identity requested the recall.

Provider/model coverage expands with NVIDIA

What changed. Provider/model coverage expands with NVIDIA onboarding/catalogs plus faster manifest-backed model/auth paths, Bedrock Opus 4.7 thinking parity, and safer Codex/OpenAI-compatible replay and streaming behavior.

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

Gateway and packaged-plugin reliability focuses

What changed. Gateway and packaged-plugin reliability focuses on slow-host startup, reusable model catalogs, event-loop readiness diagnostics, runtime-dependency repair, stale-session recovery, and version-scoped update caches.

Check it with. A catalog label for Gateway and packaged-plugin reliability focuses is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

Details behind the headline

Channel fixes cluster around Slack Block Kit limits

Channel fixes cluster around Slack Block Kit limits, Telegram proxy/webhook/polling/send resilience, Discord startup/rate-limit handling, WhatsApp delivery/liveness, and Microsoft Teams/Matrix/Feishu edge cases.

For Channel fixes cluster around Slack Block Kit limits, 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.

Security/tools

configured tool sections (tools.exec, tools.fs) no longer implicitly widen restrictive profiles (messaging, minimal). Users who need those tools under a restricted profile must add explicit alsoAllow entries; a startup warning identifies affected configs. Fixes #47487.

Treat Security/tools as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Agents/commitments

add opt-in inferred follow-up commitments with hidden batched extraction, per-agent/per-channel scoping, heartbeat delivery, CLI management, a simple commitments.enabled/commitments.maxPerDay config, and heartbeat-interval due-time clamping so magical check-ins do not echo immediately.

Use Agents/commitments 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.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Messaging and automation get active-run steering by.
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

Auto-reply/group chats. fall back to automatic source delivery when a channel precomputes message-tool-only replies but the message tool is unavailable, so Discord/Slack-style group turns do not silently complete without a visible reply. Fixes #74868. Keep the reproduction and the post-fix result together in the acceptance record.

Browser/gateway. share one browser control runtime across the HTTP control server and browser.request, and refresh browser profile config from the source snapshot, so CLI status/start honors configured browser.executablePath, headless, and noSandbox instead of falling back to stale auto-detection. Fixes #75087; repairs #73617. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.4.29-beta.2 release notes for the exact change list, then cross-check the official release index and the session concepts before acting.