OpenClaw v2026.5.19-beta.1: Agents, upgrade notes

v2026.5.19-beta.1 arrived on 2026-05-18 with a change that matters during maintenance: agents. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Before the package changes

Agents

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

Check it with. Use Agents to test ownership as well as installation. Confirm which agent owns the skill or plugin and that a missing or rejected package cannot mutate another workspace.

Dependencies

What changed. update @openclaw/proxyline to 0.3.3.

Check it with. Before relying on Dependencies, rehearse it on a disposable install. Record the schema, configuration, service owner, and exact point at which rollback is allowed or refused.

Dependencies

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

Check it with. The promise in Dependencies is only useful if the old state returns. Take a verified backup, interrupt a candidate update, and inspect both the retained package and the service.

Memory/search

What changed. scan the JS-side fallback vector path (used when the sqlite-vec index is unavailable or has a mismatched dimension) in bounded rowid batches and yield to the event loop between batches so large chunk tables can no longer pin the Node.js main thread for multi-second windows. Also keeps the SQL prepared statement rooted in a local so node:sqlite cannot finalize it mid-scan under heap pressure. Fixes #81172.

Check it with. Memory/search 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.

Details behind the headline

CLI/update

bypass npm freshness filters consistently during managed package and plugin installs so freshly published release plugins remain installable.

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

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Agents.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Create a candidate update or restore rehearsal and record which files, service, and database state it touches.
4. Check the restored files and service status, then document any case that requires a manual backup restore.
5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw doctor

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Memory/search. scan the JS-side fallback vector path (used when the sqlite-vec index is unavailable or has a mismatched dimension) in bounded rowid batches and yield to the event loop between batches so large chunk tables can no longer pin the Node.js main thread for multi-second windows. Also keeps the SQL prepared statement rooted in a local so node:sqlite cannot finalize it mid-scan under heap pressure. Fixes #81172. Keep the reproduction and the post-fix result together in the acceptance record.

CLI/update. bypass npm freshness filters consistently during managed package and plugin installs so freshly published release plugins remain installable. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.5.19-beta.1 release notes for the exact change list, then cross-check the official release index and the session concepts before acting.