Detached task runtime contract lands on mainline for safer background execution

OpenClaw Daily Brief

1. Detached task runtime becomes a first-class contract: Mainline now has explicit runtime wiring for detached tasks (building on #68886), which matters if you run longer background work and want fewer implicit side effects when plugins register outside the foreground request path.
2. Browser session attach reliability improved: Browser nodes now discover CDP websocket targets from bare ws:// endpoints before attach, and existing-session user profiles route cleanly through browser nodes in #68891, reducing brittle reconnect behavior in agent-driven browser automation.
3. Multi-agent lane contention tightened: Nested lanes are now scoped per target session, which addresses cross-agent blocking patterns, and token accounting is preserved when providers omit usage data in #67695 so usage dashboards do not silently undercount during degraded provider responses.
4. Scheduler/cron channel handling patched: Delivery state no longer persists "last" as a literal channel value, and PowerShell tool allow-lists parse correctly in #68858, removing two failure modes that can look like random no-op sends in automated runs.
5. Operator action today: If you ship from stable tags, keep production pinned to v2026.4.15. If you track main, pull through the PRs above and run a 20-minute smoke pass: one detached task, one existing-session browser attach, one concurrent multi-agent run, and one cron delivery test.

Got a tip? Send it to tips@clawnews.org