OpenClaw v2026.4.12: Security/busybox, operator field notes

The source record for v2026.4.12 names a provider, model, voice, or context change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.

Treat this as a stable maintenance checkpoint and keep the release record beside the backup and rollback evidence. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

A small field test

QA/lab

What changed. add Convex-backed pooled Telegram credential leasing plus openclaw qa credentials admin commands and broker setup docs.

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

Memory/Active Memory

What changed. add a new optional Active Memory plugin that gives OpenClaw a dedicated memory sub-agent right before the main reply, so ongoing chats can automatically pull in relevant preferences, context, and past details without making users remember to manually say "remember this" or "search memory" first. Includes configurable message/recent/full context modes, live /verbose inspection, advanced prompt/thinking overrides for tuning, and opt-in transcript persistence for debugging.

Check it with. The operator question around Memory/Active Memory is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

macOS/Talk

What changed. add an experimental local MLX speech provider for Talk Mode, with explicit provider selection, local utterance playback, interruption handling, and system-voice fallback.

Check it with. Check macOS/Talk with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Security/busybox

What changed. remove busybox/toybox from interpreter-like safe bins.

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

The details that affect a runbook

Security/Approval

prevent empty approver list from granting explicit approval authorization.

Before widening access for Security/Approval, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for QA/lab.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
4. Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

Security/busybox. remove busybox/toybox from interpreter-like safe bins. Treat the fix as a boundary condition and retain the source wording beside your local result.

Security/Approval. prevent empty approver list from granting explicit approval authorization. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.4.12 source record; the release index and session concepts remain the references to use for migrations and support boundaries.