OpenClaw 2026.5.18 adds runtime parity checks and plugin tooling

OpenClaw released version 2026.5.18 on 18 May, with 83 commits landing on main since the release cut. The update spans agents, Gateway, CLI, plugins, QA-Lab, mobile apps, messaging, and provider integrations, with a strong focus on runtime parity, release checks, and developer tooling.

One of the clearest platform changes is the dependency and runtime floor update. According to the release notes, OpenClaw updated @openclaw/proxyline to 0.3.3, moved Pi packages to 0.75.1, and raised the minimum supported Node.js 22 line to 22.19.

The build and packaging path also changed for container users. The release adds OPENCLAW_IMAGE_APT_PACKAGES as a runtime-neutral image build argument for extra apt packages, while keeping OPENCLAW_DOCKER_APT_PACKAGES as a legacy fallback. That gives Docker and Podman builds the same configuration path for additional system packages.

The release puts a lot of weight on QA-Lab, OpenClaw’s benchmark and gating suite. New scenarios now cover first-hour and optional 100-turn runtime parity, live-only canaries for workspace-read prompt compatibility, tool fixture coverage, approval-denial behavior, and local task followthrough reporting.

OpenClaw also added a dedicated openclaw qa suite --runtime-parity-tier flag and wired the standard Codex-vs-Pi tier into release checks separately from optional, live-only, and soak lanes. According to the notes, required OpenClaw dynamic runtime-tool drift now hard-fails the standard tier, and coverage reports can be surfaced with openclaw qa coverage --tools.

On the tooling side, the CLI and plugin system gained several additions. The release introduces defineToolPlugin plus openclaw plugins build, validate, and init for typed simple tool plugins with generated manifest metadata, optional tool declarations, and context factories.

Several bundled skills were added or updated as well. The release includes a meme-maker skill, node inspector debugging, fused diagram generation, throwaway spike workflow skills, and a Python debugging skill for pdb, breakpoint(), post-mortem inspection, and debugpy remote attach. The Obsidian skill now targets the official Obsidian CLI and requires its registered binary.

Gateway behavior saw a number of changes aimed at restart performance and trace clarity. According to the release notes, startup probe, config, runtime, and resource-count costs are now attributed in restart traces without changing readiness behavior, and plugin-service startup is overlapped with channel sidecars to reduce restart-ready latency while preserving /readyz gating.

There are also changes for proxy and TLS handling. OpenClaw now supports HTTPS managed forward-proxy endpoints and scoped proxy.tls.caFile CA trust for proxy endpoint TLS. On the secrets side, the Gateway uses a lighter startup path when no SecretRef values are present in the startup config.

The release includes a long list of fixes across channels and agents. Examples include better handling for Discord and Telegram follow-up turns, updated media fallback behavior, Codex app-server fixes for code mode, network access, and streamed output, and a fix that keeps approval-runtime credentials flowing through agent-owned Gateway approval calls.

OpenClaw also updated the Mac app with a redesigned Settings experience, cleaner navigation, and more consistent layout. Android Talk Mode now uses realtime Gateway relay voice sessions with streaming mic input, realtime audio playback, tool-result bridging, and on-screen transcripts.

The release notes close with a broad set of maintenance and compatibility fixes across plugins, providers, sessions, messaging, and release stability. The main headline changes in OpenClaw 2026.5.18 are the new plugin CLI flow, expanded runtime parity checks, higher Node.js requirements, and the new container image package argument.