OpenClaw 2026.5.7 tightens channels, cron, voice, and supervised agent runs

OpenClaw 2026.5.7 is not a flashy feature drop. The release notes are filed under fixes, and that is accurate. But for people running OpenClaw as an always-on assistant across chat apps, scheduled jobs, plugins, local sessions, and voice channels, this is the kind of release that changes how much supervision the system needs.

The latest public GitHub release, published May 7, 2026, focuses on making the assistant easier to inspect, harder to misroute, and less likely to claim success when the underlying delivery path failed. It also adds a few small but useful operator-facing capabilities around channel discovery, cron status, Discord voice checks, and model selection.

The practical additions

The most visible command-line change is in channel management. openclaw channels list now stays focused on channels, adds --all for bundled and catalog channels, and renders whether each channel is installed, configured, and enabled. Model auth and usage details have been moved to openclaw models auth list, openclaw status, and openclaw models list. That sounds like housekeeping, but it makes the command do one job instead of mixing setup state with provider state.

Cron also gets more machine-readable. cron list --json and cron show --json now include a computed status, so external tooling can read whether a job is disabled, running, ok, errored, skipped, or idle without reimplementing OpenClaw's status logic. For anyone treating OpenClaw scheduled jobs as production scheduled work instead of reminders, that is a meaningful addition.

Model selection gets a narrow but useful OpenAI option: openai/chat-latest can now be used as an explicit direct API-key override for trying the moving ChatGPT Instant API alias without changing the stable default model. The point is control: test the alias where you want it, not everywhere at once.

Discord voice operators get better diagnostics. OpenClaw now audits Discord voice-channel access rights in channels capabilities and channels status --probe, including auto-join targets, so missing Connect, Speak, or Read Message History access rights can be found before /vc join fails. Voice capture is also less twitchy: the default post-speech silence grace is now 2.5 seconds, with a new voice.captureSilenceGraceMs setting for noisy Discord sessions.

Safety and authorization got stricter

Several 2026.5.7 changes are about preventing the assistant from doing the wrong thing quietly. Native command handlers now honor owner enforcement. Global Active Memory toggles require admin scope. Inline tool dispatch from auto-replies now goes through before-tool-call authorization hooks. Those are not cosmetic changes; they reduce the number of places where a convenience path can bypass the policy path.

External reviewer approval handling also changes. In external reviewer approval modes, OpenClaw no longer installs the pre-guardian native PermissionRequest hook by default, which lets the external reviewer approve safe commands before OpenClaw surfaces an approval. The release also remembers allow-always decisions for identical native command-approval payloads during the active session window, and plugin approval requests now render the actual allowed decisions instead of stale options in Telegram and other native approval UIs.

Delivery reporting gets less optimistic. OpenClaw now reports deliverySucceeded=false when outbound delivery returns no adapter result, so empty or claimed delivery paths do not look like successful sends. Recurring scheduled jobs also fail implicit announce delivery before model execution when delivery.channel=last has no previous route, avoiding token spend on a job that could never deliver its result.

Channels and chat apps got a lot of cleanup

Telegram gets several fixes. Access-group sender allowlists are now honored for DMs, groups, native commands, and callback authorization before Telegram's numeric sender-ID checks. The polling watchdog is tied to getUpdates liveness so unrelated outbound Bot API calls cannot hide a wedged inbound poller. Same-chat message tool sends during an inbound Telegram turn now count as delivered when OpenClaw decides whether to emit a silent reply fallback. Provider IDs with dots also work in /models callback buttons, which matters for hf.co model lists.

WhatsApp handling improves in two places. Proactive phone-number sends can route through Baileys LID forward mappings when available, avoiding sender-only ghost chats for LID-addressed contacts. Captioned MEDIA: directive auto-replies now send once instead of first emitting an empty media message and then the captioned media reply.

Discord cross-channel sends also get a routing fix: provider-prefixed targets like discord:channel:<id> are parsed as channel sends instead of legacy DM targets, removing a path that produced misleading Unknown Channel failures.

Sessions, context, capabilities, and plugins are less stale

A recurring theme in 2026.5.7 is cache invalidation. /new and sessions.reset now clear cached capability snapshots so long-lived channel sessions rebuild the visible skill list after capabilities change. The context engine invalidates cached assembled views when source history shrinks or assembly fails, preventing pre-reset history from leaking back into the next answer. Compaction now clamps summary reserve tokens to each model's output limit, avoiding invalid max_tokens requests on high-context sessions.

Worker-session retention is now more consistent: completed session-mode subagent registry rows honor agents.defaults.worker sessions.archiveAfterMinutes rather than a hardcoded five-minute TTL. Daily gateway-agent session rollover now persists a new generated transcript file when the session id changes while preserving custom transcript paths.

Plugin publishing and installation received several reliability fixes. Release and plugin publishing retries transient ClawHub command-line dependency install failures, keeps preview-passing plugins publishable when one preview cell flakes, and verifies every expected ClawHub package version after publish. Managed plugin npm install, rollback, repair, and uninstall operations now use the same absolute POSIX npm lifecycle shell as staged package updates, avoiding cleanup failures caused by restricted PATH shells. External plugin setup entries can also forward setChannelRuntime, so deferred external channel runtime initializers are installed before startup polling.

Provider and tool fixes round out the release

The release fixes SecretRef-backed Tavily credentials for tavily_search and tavily_extract, preventing unresolved API keys from reaching those tools during exec. It also normalizes APNG-sniffed PNG uploads, preserves Gemini 3 tool-call thought-signature replay with fallback signatures, accepts legacy __env__:VAR custom-provider keys, and repairs snake_case tool-call transcript sanitization.

There are also recovery fixes: openclaw doctor --fix can repair scheduled jobs whose stored model override was default, null, blank, or JSON null, while keeping runtime validation strict. The same doctor flow preserves working OAuth-backed PI routes and recovers GPT-5 routes rewritten during 2026.5.5 when only OAuth-backed coding-provider auth is available. Gateway tasks now reconcile stale command-line run-context records whose live run context disappeared, so old task records do not block Discord, Slack, or Telegram reloads indefinitely.

Bottom line

OpenClaw describes itself as a personal AI assistant that runs on your own devices and answers through channels such as Telegram, Slack, Discord, WhatsApp, Google Chat, Signal, iMessage, Matrix, Teams, and others. A tool like that lives or dies on boring things: whether messages route to the right place, whether scheduled jobs can be observed, whether access rights are enforced, whether stale context is really gone, and whether voice joins fail before or after the user is already waiting.

That is what 2026.5.7 works on. It does not introduce a single headline feature. It makes a wide surface area less surprising.

Sources: OpenClaw 2026.5.7 GitHub release notes, published May 7, 2026; OpenClaw README.