AI Projects

OpenClaw Update 4.27: Codex Computer Use!

Published
Apr 30, 2026
Duration
10:39
Click to load the YouTube player

Video summary

Companion notes

OpenClaw 4.27 ships native Codex computer use, but only on macOS

The headline change in OpenClaw 4.27 is native Codex computer use via a bundled MCP plugin, letting the agent open browsers, click buttons, and fill forms instead of just running terminal commands. OpenClaw acts as the "pit crew" — it installs the plugin, registers marketplaces, starts the MCP server, and verifies permissions — while Codex owns the tool calls.

Fail-closed MCP checks kill silent blind turns

Before every Codex turn, OpenClaw now pings the computer use MCP server. If the server is missing, the plugin is disabled, or macOS hasn't granted permissions, the turn blocks immediately with a specific reason (e.g. "marketplace missing", "plugin disabled", "MCP server unreachable"). Pre-4.27, your turn would proceed with Codex effectively blind and you'd only notice when tokens were already burned.

The deployment gotcha: local Mac only

Codex computer use needs a real desktop with real apps. On a MacBook or Mac mini, /codex computer use status confirms readiness and the install command registers the bundled macOS marketplace. On a Linux VPS, there's no GUI to control, the MCP server reports unreachable, and fail-closed mode blocks the turn outright. VPS users still have terminal tools, headless browsers, and API integrations — just not visual desktop control.

Deep Infra joins bundled providers, plus reliability patches

Deep Infra is now a one-click toggle provider — no manual endpoint or API key setup. Telegram's startup/send bug (agents going unresponsive) and Slack's dropped connections + frozen media uploads are patched. The update sync double-processing bug and the false "ready" flag on cold sessions are fixed. Windows restarts no longer leave orphan processes.

SDK normalization and the upgrade warning

The OpenClaw plugin SDK now exposes a channel route normalization helper so Slack channel IDs, Discord snowflakes, and Telegram chat IDs don't each need bespoke routing logic. The dependency tree got a refresh. If openclaw update breaks, the creator says to run openclaw doctor --fix — older plugins with implicit startup loading, custom scripts importing from old internal paths, and pinned non-standard history defaults are the usual suspects.

Watch on YouTube

Prefer the native player? Open it on YouTube: https://www.youtube.com/watch?v=qac5ChGLgTU