ZeroClaw merges multi-session panes that keep background agent work alive

ZeroCode is moving beyond a single live conversation per chat-like pane. A September 9 merge adds multiple session states and an agent sidebar for opening, focusing, monitoring and closing them. The product change is straightforward: switching attention should no longer mean replacing the conversation that was already working.

The inspected implementation description spends considerable space on what happens when that promise meets disconnects and late messages. It retains unsent drafts and selected files, correlates completion with the correct turn generation, and keeps durable daemon history authoritative. That makes the sidebar a view of real concurrent work rather than a second collection of optimistic status labels that can diverge from the runtime.

The facts

- PR #9739 merged on September 9 at 09:39:55 UTC; the stable-release baseline remains v0.8.5 published September 5. - Each live Chat or ACP session keeps its own transcript, queue, pending interactions, errors, drafts and attachments. - The sidebar opens, focuses, closes and monitors sessions, including an explicit Running state. - Daemon session history remains canonical while client ChatState owns client-only queues and interaction state. - Additive RPC fields cover lifecycle recovery and optional generation/count correlation; older peers may omit them. - Reusing a still-live session ID in the same mode now rebinds to that session rather than replacing its in-memory history. - Queue, plan and deletion controls in the sidebar remain outside this change.

Why it matters

Multi-agent interfaces are only useful if switching views does not silently change execution ownership. A late finish notification that marks newer work Ready, or a reconnect that loses a background queue, can mislead an operator more effectively than an obvious crash. This merge ties the new visual workspace to explicit session and turn lifecycles. It also exposes a compatibility detail worth noticing: same-ID reuse has different semantics even though several wire fields are additive and optional.

Current

Inspected on 2026-09-10. The ZeroClaw stable-release baseline is v0.8.5 published 2026-09-05T07:31:19Z. The main source was merged 2026-09-09T09:39:55Z when captured. Release metadata is a version boundary; an open proposal, a merged mainline change and a packaged release remain different states.

Evidence

The primary evidence is zeroclaw-labs/zeroclaw PR #9739 (https://github.com/zeroclaw-labs/zeroclaw/pull/9739). Supporting context comes from zeroclaw-labs/zeroclaw issue #9729 (https://github.com/zeroclaw-labs/zeroclaw/issues/9729); zeroclaw-labs/zeroclaw issue #9730 (https://github.com/zeroclaw-labs/zeroclaw/issues/9730); ZeroClaw — current official README (https://raw.githubusercontent.com/zeroclaw-labs/zeroclaw/master/README.md). These pages were inspected directly. Related project records explain the source cluster; they are not independent replications of contributor test claims.

Operator take

When the change reaches the build you use, test two active conversations before relying on the sidebar for supervision. Disconnect with an unsent draft and attachment, reconnect, then finish an older turn while another remains active. Check the daemon’s durable transcript against the visible state. Hiding the sidebar is not a rollback of the multi-session behavior; the source explicitly says those lifecycle changes have no separate toggle.

Caveat

The merge timestamp is confirmed in captured GitHub metadata, but this is not a new packaged-release announcement. The PR contains validation from several identified revisions and stale pre-merge checklist text. Those reported tests and screenshots must not be combined into an invented fresh full-suite result; illmethinks did not rerun them.