OpenClaw v2026.5.19-alpha.1: Agents, boundary review

The security lens for v2026.5.19-alpha.1 is its trust boundary. The official record describes an access, approval, or trust-boundary change; this reading keeps the exact tag visible and turns the source bullets into checks an operator can actually repeat.

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.

Boundary review

01 / Agents

Source signal. clarify that fixes should default to clean bounded refactors, lean internals, and explicit plugin SDK/API deprecation paths.

The maintainer check for Agents is a complete package review: identify the entry point, requested access, dependency tree, and uninstall behavior before publishing or upgrading.

02 / Dependencies

Source signal. update @openclaw/proxyline to 0.3.3.

Test Dependencies with a failure you can explain. Confirm that the prior configuration and data remain readable, then document the cases where an operator must restore manually.

03 / Dependencies

Source signal. update Pi packages to 0.75.1 and raise the minimum supported Node.js 22 line to 22.19.

Treat Dependencies as a recovery contract: identify what is preserved, what is irreversible, and which post-update check decides whether the old package may be activated.

04 / CLI

Source signal. reject explicit port numbers above 65535 before they reach Gateway or Node bind paths. Fixes #83900.

Measure CLI before and after the update with synthetic data, and explain every accepted finding in the release record.

What the implementation list adds

Codex app-server

preserve plugin tool auth profiles when Codex owns model transport so OpenClaw dynamic tools can resolve their provider credentials.

Before widening access for Codex app-server, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Agents.
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 security audit

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

CLI. reject explicit port numbers above 65535 before they reach Gateway or Node bind paths. Fixes #83900. Treat the fix as a boundary condition and retain the source wording beside your local result.

Codex app-server. preserve plugin tool auth profiles when Codex owns model transport so OpenClaw dynamic tools can resolve their provider credentials. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.5.19-alpha.1 source record; the release index and Gateway security guide remain the references to use for migrations and support boundaries.