v3.20.0
Added
-
Experimental: hidden panes can skip output parsing (Settings → "Skip hidden pane rendering"). Even with the shared output scheduler, hidden agents' output was still parsed eventually — and measurement showed that parsing total is what drags the visible pane once several background agents stream at once (4 hidden flooders pulled the visible pane down to ~10–20fps). With this toggle on (daemon sessions only, default off), hidden panes' output is queued but never parsed: the renderer does no parsing work for panes you aren't looking at. A pane whose backlog outgrows its cap is marked stale and transparently re-synchronized from the daemon's session buffer when revealed — the daemon replays the authoritative bytes onto a reset terminal, so what you see on reveal is the pane's true current state, never a duplicate or a half-parsed frame. Agent-facing buffer reads (
wmux_search_panes,terminal_read) hydrate a stale pane before reading so orchestrating agents never see old output. If a re-sync can't complete (dead session, legacy daemon), the pane degrades to its last-known screen instead of sticking or losing its identity. -
Diff comments now wake the task agent (J4). Commenting on a hunk in a fan-out task's diff surface no longer just records a note — it @-mentions the task's agents on the mission-channel post, so the existing mention→wake loop nudges them to read and act on the feedback. Every non-human member of the mission channel (excluding you, the commenter) is mentioned at the workspace level, so multiple agent panes sharing one workspace all get woken; if every agent has left the channel the comment still posts, just without a mention. The post's body also carries a
[diff: <file> @ <hunk>] <comment>prefix so an agent reading the channel over the CLI or MCP (which don't render the structured anchor) still sees which file and hunk the comment is about. The success message reports how many agents were pinged. -
Fleet cards surface an agent's completion evidence. A fleet card now shows a small
✓ evidence n/mbadge when the pane's most recently completed A2A task carries structured completion evidence —nis how many of themevidence items are actually verified (a passed command, or a verified inspection/artifact). It's the "trust it ran unattended" proof made legible on the card: the check reads green once at least one item is verified and stays muted when nothing is (verified is a grade, not a claim), and the task title plus the evidence summary live in the badge's tooltip so the on-card text stays a single compact token. The badge reads existing task state only (no new store or round-trip), is addressed per-pane (a pane-pinned task shows on exactly that pane; a workspace-level task shows on the workspace's active pane), and simply isn't drawn when there's no such task.
Fixed
-
Multiple workspaces full of busy agents no longer stutter the visible terminal. Every pane used to push its PTY output straight into its own terminal the moment it arrived over IPC — including panes in hidden workspaces — so a fleet of background agents ran that many independent parse/render pipelines on the one renderer thread, and the pane you were actually typing into starved between them. Terminal output now flows through a single shared scheduler: the visible pane keeps the exact direct-write path it always had for ordinary output (zero added latency), while hidden panes' output is batched and drained cooperatively under a hard per-tick time budget, so no amount of background agent chatter can pin the UI. Even the visible pane's own output floods are chunked through that budget rather than parsed in one blocking pass, so watching a chatty agent stays responsive too. Nothing is dropped — a hidden pane's backlog is handed over in full when it becomes visible (before its reveal repaint), when a reconnect replay needs it, or if it ever exceeds the scheduler's memory cap (which simply restores the old behavior for that pane).
-
Diff-panel comments now actually post to the mission channel. The diff comment post omitted the
senderidentity the daemon requires, so every comment was rejected with a "코멘트 발사 실패" authorization error instead of being recorded. The comment now posts as the diff's owner workspace (its own mission-channel member row), which is also what lets the new @-mention wake the agent.
Security
events.pollno longer lets an agent eavesdrop on another workspace's channels (audit B3). The event-poll RPC previously scoped its results by a caller-suppliedworkspaceId, so a same-user pipe/MCP client could live-subscribe to any workspace's private channel messages, channel lifecycle, and A2A task pointers just by naming that workspace's id — no pane identity required. Those confidentiality-sensitive event types are now scoped to a server-resolved workspace derived from the caller's verifiedsenderPtyId(the same identity anchor thea2a.channel.*mutations already use), and the caller-suppliedworkspaceIdis ignored for them; an unresolvable caller receives none of these events (fail-closed). The bundled MCPwmux_events_polltool forwards its own PID-walkedsenderPtyId, so a legitimately-placed agent still sees its own channels and tasks unchanged. The first-party operator surface (the app's own renderer/plugin host) keeps scoping across the local workspaces it names. Ordinary lifecycle events (pane/process/agent/workspace metadata) are unaffected — their all-workspace firehose was already reachable by anyevents.subscribesubscriber, so their workspace scope was never a confidentiality boundary and external lifecycle subscribers keep working.