OpenClaw 2026.5.7 fixes release hardens plugins, cron, and Telegram

OpenClaw 2026.5.7 focuses on fixes across publishing, automation, messaging, and runtime state handling. The release was posted on May 7, 2026, and includes changes aimed at making failed operations easier to recover, while reducing cases where partial state could confuse users or tooling.

On the plugin side, OpenClaw now retries transient ClawHub CLI dependency install failures during release and publishing. The company also said preview-passing plugins remain publishable even if one preview cell flakes, and every expected ClawHub package version is verified after publish so maintenance releases are less likely to hide a partial publish.

For users testing models, OpenClaw added support for openai/chat-latest as an explicit direct API-key model override. That lets users try the moving ChatGPT Instant API alias without changing the stable default model.

Several command-line tools were updated to expose more state to external automation. The Cron CLI now includes computed status in incron list --json and cron show --json output, so other tooling can read disabled, running, ok, error, skipped, and idle states without rebuilding status logic.

The Channels CLI was also trimmed and reorganized. OpenClaw said openclaw channels list is now channel-only, with --all adding bundled and catalog channels, and installed, configured, and enabled state now rendered there. Model auth and usage details moved to openclaw models auth list, openclaw status, and openclaw models list.

OpenClaw also made a series of runtime and access-control changes. Native command handlers now honor owner enforcement. Global Active Memory toggles require admin scope. Inline skill tool dispatch in auto-reply now goes through before-tool-call authorization hooks, and Telegram authorization now respects accessGroup:* sender allowlists before Telegram’s numeric sender-ID checks.

Session handling and cached state were cleaned up in multiple places. Gateway sessions now clear cached skills snapshots during /new and sessions.reset so long-lived channel sessions rebuild the visible skill list after skills change. OpenClaw also invalidates cached assembled context views when source history shrinks or assembly fails, preventing stale pre-reset history from being reused.

The release fixes several delivery and messaging edge cases. Discord message routing now parses provider-prefixed targets like discord:channel:<id> as channel sends, which prevents cross-channel send actions from being misrouted into misleading Unknown Channel failures. Agent delivery now reports deliverySucceeded=false when outbound delivery returns no adapter result, and isolated cron runs now fail before model execution if delivery.channel=last has no previous route.

OpenClaw made additional fixes for Cron, plugins, Telegram, Discord voice, WhatsApp, and Codex approval flows. Cron doctor --fix can repair persisted jobs whose payload.model was stored as default, null, blank, or JSONnull. Discord voice permissions now show up in channels capabilities and channels status --probe, while the voice capture default pause after speech was extended to 2.5 seconds.

The company also changed approval behavior in Codex modes, stopped installing the pre-guardian native PermissionRequest hook by default, and said plugin approval requests now validate their actual allowed decisions so Telegram and other native approval UIs do not show stale actions. OpenClaw 2026.5.7 also includes updates for Tavily credentials, WhatsApp message routing, model provider parsing, and Telegram model callback buttons.