OpenClaw v2026.4.19-beta.2: Nested lanes, upgrade notes

v2026.4.19-beta.2 arrived on 2026-04-19 with a change that matters during maintenance: nested lanes. 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/openai-completions

What changed. always send stream_options.include_usage on streaming requests, so local and custom OpenAI-compatible backends report real context usage instead of showing 0%.

Check it with. Check Agents/openai-completions 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.

Agents/nested lanes

What changed. scope nested agent work per target session so a long-running nested run on one session no longer head-of-line blocks unrelated sessions across the gateway.

Check it with. Measure Agents/nested lanes after a fresh session and after a reconnect. The record should say what was retained, what was intentionally absent, and which identity requested the recall.

Details behind the headline

Read the narrow change in context

v2026.4.19-beta.2 is a pre-release checkpoint with a deliberately small surface. The source names Agents/openai-completions: always send stream_options.include_usage on streaming requests, so local and custom OpenAI-compatible backends report real context usage instead of showing 0%. A narrow patch still has a clear job: it should remove one failure or preserve one compatibility promise without changing unrelated configuration.

Keep this patch beside the upgrade and rollback record. Compare the installed tag, package version, and service owner before applying it. If this entry is a correction release, record the broken behavior that led you here, then repeat that exact scenario after the update. That evidence is more useful than a general claim that the package installed successfully.

The adjacent source detail is Agents/nested lanes: scope nested agent work per target session so a long-running nested run on one session no longer head-of-line blocks unrelated sessions across the gateway. Read both signals together, because a hotfix can alter the boundary around a plugin, channel, session, or installer even when the version number looks like a minor suffix.

A small worksheet for this version

• Write the old version, the new version, and the package or tag that actually changed.
• Capture one reproduction before the update and the same reproduction after it.
• Record the first useful log line, the final user-visible result, and any rollback command that was tested.
• Leave unrelated channels, skills, and provider defaults untouched until the correction is understood.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Agents/openai-completions.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Run a read-only prompt with a known answer and save provider, model, reasoning, and latency details.
4. Change only the candidate route, then confirm that a failed request returns a readable error and leaves the session intact.
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 models

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

Agents/openai-completions. always send stream_options.include_usage on streaming requests, so local and custom OpenAI-compatible backends report real context usage instead of showing 0%. Keep the reproduction and the post-fix result together in the acceptance record.

Agents/nested lanes. scope nested agent work per target session so a long-running nested run on one session no longer head-of-line blocks unrelated sessions across the gateway. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.4.19-beta.2 release notes for the exact change list, then cross-check the official release index and the model provider reference before acting.