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

v2026.4.29 changes how an agent selects, calls, or remembers a provider. The official record describes a provider, model, voice, or context change; the useful test is a small request with the provider boundary recorded.

This is a stable release line; read the exact record for migrations and fixes before applying it to a live Gateway. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

Provider and model consequences

01 / Messaging and automation get active-run steering by

Source signal. 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.

Messaging and automation get active-run steering by 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.

02 / Memory grows into a people-aware wiki with provenance

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

Memory grows into a people-aware wiki with provenance changes what a run can carry forward. Use synthetic names, inspect both recalled and omitted context, and check which workspace or participant can read it.

03 / Provider/model coverage expands with NVIDIA

Source signal. 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.

Treat Provider/model coverage expands with NVIDIA as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

04 / Gateway and packaged-plugin reliability focuses

Source signal. 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.

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.

What changes outside the chat box

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.

The operator question around Channel fixes cluster around Slack Block Kit limits is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

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.

Read Security/tools as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

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.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Messaging and automation get active-run steering by.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Use a disposable conversation for one send, one reconnect, and one retry; keep the destination identifiers with the result.
4. Leave the channel disabled after the test if its credentials or pairing were created only for this rehearsal.
5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

Providers/OpenAI Codex. preserve existing wrapped Codex streams during OpenAI attribution so PI OAuth bearer injection reaches ChatGPT/Codex Responses, and strip native Codex-only unsupported payload fields without touching custom compatible endpoints. Record the failure that this correction addresses before declaring the upgrade complete.

Agents/tool-result guard. use the resolved runtime context token budget for non-context-engine tool-result overflow checks, so long tool-heavy sessions no longer compact early when contextTokens is larger than native contextWindow. Fixes #74917. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.4.29 GitHub release. The release index gives the surrounding sequence, while the session concepts supplies the operational background.