Fix cross-agent subagent channel routing

## What changed OpenClaw released a fix for cross-agent subagent channel routing on 19 May 2026. The update routes subagent spawns through the target agent's bound channel account instead of the caller's account.

This prevents child sessions from pulling the wrong messaging credentials in shared workspaces. The change targets multi-user setups where multiple agents run under one installation.

## Why it matters Shared workspaces often mix personal and team agents on the same VPS. Incorrect channel inheritance broke notifications and task handoffs when one agent spawned another.

The fix reduces silent failures that previously required manual account checks after every subagent launch. It strengthens OpenClaw's claim as a reliable runtime for mixed personal and small-team automation without forcing separate installs.

## How to use it Pull the latest code from the GitHub repository and restart the agent process. No YAML changes are required for existing channel bindings.

Confirm the update by spawning a test subagent from a secondary workspace and checking that messages arrive on the intended account. The fix ships in the current main branch and is available immediately for self-hosted users.

## Watch for Monitor error logs for any remaining channel mismatches during the next two weeks. A follow-up release is likely to add explicit workspace isolation toggles in the CLI config. Test subagent creation in your heaviest shared setup first to validate the routing before relying on it for production tasks.