OpenClaw 2026.4.27 adds Codex Computer Use, DeepInfra provider, manifest-first plugins
TL;DR
OpenClaw 2026.4.27 ships Codex Computer Use setup, DeepInfra as a bundled provider, Tencent Yuanbao and QQBot support, and manifest-first plugin metadata that reduces Gateway boot work.
What changed
OpenClaw 2026.4.27 (April 29, 2026) adds Codex Computer Use setup with status and install commands, marketplace discovery, and fail-closed MCP checks. DeepInfra joins as a bundled provider with model discovery, media generation, TTS, embeddings, and provider-owned onboarding policy. Tencent Yuanbao and QQBot expand messaging coverage. Plugin startup moves toward manifest-first metadata so Gateway boot work drops and provider rows become easier to audit. A long list of reliability fixes covers Telegram startup, Slack socket and media stalls, gateway prewarm, session and history defaults, update sync, and Windows restart handoffs.
Why it matters
The manifest-first plugin shift is the strategic change. Provider routing tables, model-id normalization, and request-family hints are migrating out of core and into plugin manifests. That means new provider integrations stop requiring a fork-and-PR cycle through the OpenClaw core repo and become plugin operations. For anyone maintaining a custom OpenClaw fork or running heavy plugin loadouts, boot time drops and provider drift gets easier to track.
What to watch for
If you run Codex Computer Use, the new setup commands are worth adopting; the fail-closed MCP checks catch desktop control misconfigurations early. If you use DeepInfra, drop the third-party plugin and use the bundled one; it gets first-party update flow. Skim the reliability fix list against your active platforms (Telegram, Slack, iOS background nodes) and upgrade if any of those bugs hit your install.
Who this matters for
- Developers: Adopt 2026.4.27 if you run Codex Computer Use desktop agents (now ships with install + status commands), DeepInfra as a first-class provider, or run plugin-heavy installs that have been slow to boot.
What to watch next
OpenClaw is moving fast: 2026.4.27 lands the Codex Computer Use setup commands, DeepInfra as a bundled provider with media gen and embeddings, and the start of a manifest-first plugin model. The manifest shift is the longest-tailed change. Once provider rows, aliases, and suppressions live in manifests instead of being hardcoded into core, plugin maintainers can ship new provider integrations without forks.
Reliability fixes are the unsung hero here: Telegram startup, Slack socket stalls, gateway prewarm, Windows restart handoffs. None of those are headline features, but they are the bugs that take a working install and turn it into a paged outage at 2am. Skim the changelog for anything affecting your stack and upgrade if you hit any of the named issues.
by Harsh Desai
About openclaw
View the full openclaw page →All openclaw updatesMore from openclaw
- App UpdateOpenClaw 2026.4.25 lands TTS upgrade, OpenTelemetry coverage, browser hardening
OpenClaw 2026.4.25 ships a TTS upgrade with /tts latest, chat-scoped auto-TTS, six new voice providers, OpenTelemetry coverage across the agent loop, browser automation hardening, and PWA / Web Push support.
- App UpdateOpenClaw 2026.4.26 ships browser realtime transport, Cerebras, asymmetric embeddings
OpenClaw 2026.4.26 ships a generic browser realtime transport contract with Google Live Talk sessions, Cerebras as a bundled provider, asymmetric embedding endpoint config, and provider-filtered model routing.
- App UpdateOpenClaw 2026.4.20 adds session pruning, cron fixes, subagent reporting
OpenClaw 2026.4.20 prevents OOM from cron backlog, handles cron modes correctly, adds failure context, and fixes PowerShell parsing on Windows for better stability.