OpenClaw v2026.4.19-beta.1: Channels, interface notes

v2026.4.19-beta.1 changes a surface that users can see. The release record describes a channel, client, interface, or browser change; this article follows the state behind the screen instead of treating a new button as proof that the workflow is complete.

Because this is a pre-release, use a disposable Gateway first and leave the stable version available for comparison. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

State that a reader can see

Agents/channels

What changed. route cross-agent subagent spawns through the target agent's bound channel account while preserving peer and workspace/role-scoped bindings, so child sessions no longer inherit the caller's account in shared rooms, workspaces, or multi-account setups.

Check it with. Use Agents/channels as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

Telegram/callbacks

What changed. treat permanent callback edit errors as completed updates so stale command pagination buttons no longer wedge the update watermark and block newer Telegram updates.

Check it with. For Telegram/callbacks, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

The wiring behind the screen

Read the narrow change in context

v2026.4.19-beta.1 is a pre-release checkpoint with a deliberately small surface. The source names Agents/channels: route cross-agent subagent spawns through the target agent's bound channel account while preserving peer and workspace/role-scoped bindings, so child sessions no longer inherit the caller's account in shared rooms, workspaces, or multi-account setups. 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 release line it belongs to. 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 Telegram/callbacks: treat permanent callback edit errors as completed updates so stale command pagination buttons no longer wedge the update watermark and block newer Telegram updates. 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.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Agents/channels.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Use a disposable conversation for one send, one reconnect, and one retry; keep the destination identifiers with the result.
4. Leave the channel disabled after the test if its credentials or pairing were created only for this rehearsal.
5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw doctor

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

Agents/channels. route cross-agent subagent spawns through the target agent's bound channel account while preserving peer and workspace/role-scoped bindings, so child sessions no longer inherit the caller's account in shared rooms, workspaces, or multi-account setups. Record the failure that this correction addresses before declaring the upgrade complete.

Telegram/callbacks. treat permanent callback edit errors as completed updates so stale command pagination buttons no longer wedge the update watermark and block newer Telegram updates. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.4.19-beta.1 GitHub release. The release index gives the surrounding sequence, while the channel routing guide supplies the operational background.