OpenClaw’s May 14 queue is a reminder that multi-channel agents fail at the seams
Fresh OpenClaw issues and PRs are less about one headline feature and more about the seams that decide whether a personal agent is safe to leave running. Issue #81484 reports a Discord guild regression in 2026.5.7 where server-channel prompts can produce perpetual typing, malformed sends missing the message payload, duplicate replies, or runaway outbound loops. Issue #81480 says `gateway.tailscale.mode: off` is ignored, with `sudo tailscale serve` still called roughly every three seconds — about 43,000 sudo invocations per day. Issue #81472 consolidates five config gaps found while splitting agents by role: per-agent bootstrap fields validate but do not take effect, and channel groupPolicy / dmPolicy behavior differs across schema, runtime, and patch CLI. Nearby fixes show the same shape: #81479 bridges resolved Gateway auth into isolated Codex app-server subprocesses, #81477 makes message actions use the resolved SecretRef runtime snapshot, #81488 hardens node exec approval prechecks so gateway-local PATH does not influence node-host decisions, #81486 clears Telegram progress drafts before final replies, and #81482 keeps ACPX one-shot clients alive long enough for the initial turn.
The interesting pattern is not a single bug. It is that OpenClaw is pushing deeper into multi-channel, multi-agent, and isolated-runtime operation, where tiny mismatches between schema, resolved secrets, session routing, and adapter lifecycle become user-visible trust failures. These are exactly the bugs that turn an otherwise capable agent into something operators hesitate to leave unattended.
- Issue #81484 describes Discord guild replies that can hang, send malformed payloads, duplicate, or loop until gateway restart
- Issue #81480 reports `gateway.tailscale.mode: off` still triggering `sudo tailscale serve` around every three seconds, producing roughly 43,000 sudo calls per day
- Issue #81472 documents five per-agent bootstrap and channel-policy inconsistencies found during a worker/coordinator split
- PR #81479 injects resolved Gateway auth into isolated Codex stdio app-server environments without copying SecretRef files
- PR #81477 routes message.action through the active resolved-secrets runtime snapshot; PR #81488 makes node exec approval prechecks use the forwarded node env instead of gateway PATH
- PRs #81486 and #81482 cover Telegram progress-draft cleanup and ACPX one-shot initial-turn lifecycle gaps
- Several items are still open PRs or open issues, so installed builds may not include the fixes
- The strongest evidence is operator reports and targeted regression tests, not a consolidated release note yet
- Some bugs only appear with real Discord guilds, Tailscale, SecretRef-backed auth, or ACP adapters, so local CLI tests can miss them