OpenClaw v2026.5.14-beta.1: Dependencies, delivery notes

v2026.5.14-beta.1 is a channel and session story. The official source describes a channel, client, interface, or browser change, and the important question is what survives the handoff between a Gateway, a conversation, and a reconnect.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

Follow the message path

Dependencies

What changed. route root ambient Node proxy agents through @openclaw/proxyline and drop root proxy-agent, https-proxy-agent, and minimatch dependencies.

Check it with. Keep Dependencies measurable: name the input, expected output, failure signal, and operator who approved the test before calling the change ready.

Control UI/i18n

What changed. add a pnpm ui:i18n:report baseline report for hardcoded-copy focus areas and locale fallback metadata.

Check it with. For Control UI/i18n, inspect state rather than only the new control. Repeat the flow after reload and reconnect, and note the session, pending action, URL, and visible error.

Maintainer tooling

What changed. add a repo-local codex-review skill for Codex closeout reviews, including local dirty-work and PR-branch review helpers that rerun until no accepted/actionable findings remain and avoid unsupported inline prompts with --base.

Check it with. Check Maintainer tooling with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Cron/Codex

What changed. default exact-command scheduled agent turns to lightweight bootstrap context so automation runs the command before loading workspace identity or memory context.

Check it with. Check Cron/Codex with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

The less visible details

Codex plugin/Gateway

strip unpaired UTF-16 surrogates from Codex app-server JSON-RPC payloads and let stale reply-work recovery abort stalled reply runs, preventing malformed media turns from wedging gateway lanes.

The safe reading of Codex plugin/Gateway is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Dependencies.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Exercise the named capability with a non-sensitive prompt, including the fallback or refusal result if it occurs.
4. Force a timeout or provider fallback in a disposable session and verify that no side effect is repeated.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw models

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

Cron/Codex. default exact-command scheduled agent turns to lightweight bootstrap context so automation runs the command before loading workspace identity or memory context. Treat the fix as a boundary condition and retain the source wording beside your local result.

Codex plugin/Gateway. strip unpaired UTF-16 surrogates from Codex app-server JSON-RPC payloads and let stale reply-work recovery abort stalled reply runs, preventing malformed media turns from wedging gateway lanes. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.5.14-beta.1 source record; the release index and channel routing guide remain the references to use for migrations and support boundaries.