OpenClaw v2026.5.14-beta.2: Config, for maintainers

For maintainers reading v2026.5.14-beta.2, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.

This candidate is still pre-release. Treat provider, channel, and migration behavior as unconfirmed until your own bounded test passes. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Compatibility for maintainers

01 / Channels/SDK

Source signal. add normalized command turn facts to channel turn construction and expose command-turn helpers for plugin inbound contexts.

Channels/SDK lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

02 / Agents/config

Source signal. support per-agent bootstrap profile overrides for contextInjection, bootstrapMaxChars, and bootstrapTotalMaxChars, inheriting from agents.defaults when omitted. Fixes #69966.

Agents/config changes what a run can carry forward. Use synthetic names, inspect both recalled and omitted context, and check which workspace or participant can read it.

03 / Dependencies

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

A release note about Dependencies becomes useful when the same task can be repeated after a restart and still produce an explainable result.

04 / Models/providers

Source signal. trust the exact configured custom/local provider baseUrl origin for guarded model HTTP requests, so loopback, LAN, tailnet, and private DNS endpoints work without broad private-network access while different ports and metadata/link-local pivots remain blocked. Fixes #80732.

Before widening access for Models/providers, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

API, package, and test clues

Bind shell script operands after combined options [AI]

The release records a focused fix in bind shell script operands after combined options [ai].

A release note about Bind shell script operands after combined options [AI] becomes useful when the same task can be repeated after a restart and still produce an explainable result.

Run the smallest useful rehearsal

1. Write down the baseline for Channels/SDK, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw models

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Fix details to carry forward

Models/providers. trust the exact configured custom/local provider baseUrl origin for guarded model HTTP requests, so loopback, LAN, tailnet, and private DNS endpoints work without broad private-network access while different ports and metadata/link-local pivots remain blocked. Fixes #80732. This is the edge case to include in a regression check, especially when the release is pre-release.

Bind shell script operands after combined options [AI]. The release records a focused fix in bind shell script operands after combined options [ai]. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.5.14-beta.2 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.