Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.
TypeScript adhdagent-orchestrationai-agentscanvasclaude-codecodexcoding-agentsdeveloper-toolselectrongeminilinuxmacosmultiplexeropencodeparallel-agentsterminalterminal-emulatorterminal-multiplexertmuxworkspace-manager
docs(release-notes): correct four v0.5.0 claims against the code
revieweb36d41e7b0e
diff --git a/docs/release-notes/v0.5.0.md b/docs/release-notes/v0.5.0.mdindex 5f32e72dc..e989011e3 100644--- a/docs/release-notes/v0.5.0.md+++ b/docs/release-notes/v0.5.0.md@@ -1,31 +1,32 @@**The ⌘M chat view became a reading surface.** Six changes rebuilt it. A busy turn used to be awall of `Bash` / `Read` chips with nothing saying why: now a run of two or more consecutive tool-calls folds into one closed block that names its own count ("4 tool calls Bash ×2, Skill, …"),-and Claude's thinking summaries print between the runs, dimmed, the way the TUI does. Code blocks-are syntax-colored through Monaco, loaded only when the first fenced block appears, and Copy still-copies the exact source — if the colored output does not match the source text the block stays-plain rather than hand you something subtly wrong. An `Edit` or `Write` call draws its diff in the-thread. Pasted images show as thumbnails. Thinking folds carry a real duration ("Thought for 1m-35s"), measured against 1,037 records across CLI 2.1.275–2.1.316. User bubbles carry a clock time-and the thread has day dividers. A context compaction is a chip saying `274430 → 16889 tokens`-instead of the summary wall. Page Up / Page Down scroll it, and a pill tells you how many messages-landed while you were scrolled up. One fix in there is worth naming on its own: a one- or two-word-answer typed into the view — `a`, `c`, `yes` — often sat unsent in Claude's composer, because the-old send waited for the text to appear *more times on the whole screen*, and typing `a` also-removed the one in "agents" from the status line. The composer itself is read now. The todo-list-card is in the build but inert: the measuring host held zero `TodoWrite` records, because current-CLIs write `TaskCreate`/`TaskUpdate` instead.+calls folds into one closed block that names its own count ("6 tool calls Bash ×4, Read ×2", and+"+N more" past the third name), and Claude's thinking sits in the gaps between the runs as a+closed, dimmed fold labelled with how long it took. Code blocks are syntax-colored through Monaco,+loaded only when the first fenced block appears, and Copy still copies the exact source — if the+colored output does not match the source text the block stays plain rather than hand you something+subtly wrong. An `Edit` or `Write` call draws its diff in the thread. Pasted images show as+thumbnails. Thinking folds carry a real duration ("Thought for 1m 35s"), measured against 1,037+records across CLI 2.1.275–2.1.316. User bubbles carry a clock time and the thread has day+dividers. A context compaction is a chip — `Compaction · auto`, with `274430 → 16889 tokens`+inside — instead of the summary wall. Page Up / Page Down scroll it, and a pill tells you how many+messages landed while you were scrolled up. One fix in there is worth naming on its own: a one- or+two-word answer typed into the view — `a`, `c`, `yes` — often sat unsent in Claude's composer,+because the old send waited for the text to appear *more times on the whole screen*, and typing+`a` also removed the one in "agents" from the status line. The composer itself is read now. The+todo-list card is in the build but inert: the measuring host held zero `TodoWrite` records,+because current CLIs write `TaskCreate`/`TaskUpdate` instead.**Liquid Glass stopped fighting the GPU.** A `backdrop-filter` re-runs every time its surface is-drawn, and a terminal is drawn for every line it prints — so each streaming terminal re-blurred its-own glass at frame rate, and the damage spread to the glass around it. Terminal glass is now a+drawn, and a terminal is drawn for every line it prints — so each streaming terminal re-blurred+its own glass at frame rate, and the damage spread to the glass around it. Terminal glass is now astatic, downsized copy of the wallpaper under the same filter chain, which Chromium draws once andreuses, and the SVG refraction filter runs only on the Clear side of the Readable tick, where it-actually displaces anything. Measured on an M2 Air with six glass terminals: one terminal streaming-went from 71% GPU to **20%**, six from 92% to **42%**, with CPU halved in both. The honest trade:-a glass node no longer shows a node it overlaps — it frosts the wallpaper only — and its outermost-1–2px are slightly lighter. A focused node, an aerial wallpaper and Reduce Transparency keep the-live backdrop.+actually displaces anything. Measured on an M2 Air with six glass terminals: one terminal+streaming went from 71% GPU to **20%**, six from 92% to **42%**; CPU went 32% to 20% for one+terminal and 100% to 50% for six. The honest trade: a glass node no longer shows a node it+overlaps — it frosts the wallpaper only — and its outermost 1–2px are slightly lighter. A focused+node, an aerial wallpaper and Reduce Transparency keep the live backdrop.**Focus mode has arrows.** In focus mode, ⌘←/→/↑/↓ move to the neighbouring terminal and you stayin focus mode; a switch used to be ⌘⇧F, ⌘→, ⌘⇧F. It swaps the node rather than flying the camera,@@ -33,13 +34,13 @@ because the canvas pane is hidden in focus mode and framing a node on a zero-sizjump-to-origin bug.**A station can wake the agent that opened it.** Two changes close the same gap from either side.-`report-outcome --notify-opener` sends the opener one notice written by nodeterm, so an orchestrator-that ended its turn after opening stations is woken when they report instead of polling; only a-*changed* outcome notifies, so a station repeating itself cannot keep waking anyone, and the-station's reply says whether its opener heard — told, told when idle, or could not be told, with the-reason. Separately, a station on the Server Edition can now `reply` to its orchestrator at all: the-delivery gate required the caller to have opened the target, and a station never opens its opener.-`send` and `notify` are unchanged.+`report-outcome --notify-opener` sends the opener one notice written by nodeterm, so an+orchestrator that ended its turn after opening stations is woken when they report instead of+polling; only a *changed* outcome notifies, so a station repeating itself cannot keep waking+anyone, and the station's reply says whether its opener heard — told, told when idle, or could not+be told, with the reason. Separately, a station on the Server Edition can now `reply` to its+orchestrator at all: the delivery gate required the caller to have opened the target, and a+station never opens its opener. `send` and `notify` are unchanged.**There is a free-tier project limit in this build, and it is off.** A free desktop install willeventually be limited in how many projects it keeps open at once; Pro is unlimited, and installs@@ -48,8 +49,8 @@ verified offline. None of it does anything yet: it stays dormant until the servesigning key and has a cutoff set, and while dormant every way of opening a project behaves exactlyas before, synchronously, asking nobody and writing nothing. The machine is identified only by asalted hash of the OS machine id. **Nothing is ever force-closed** — the gate only refuses a new-open; no project, node or tmux session is closed, deleted or detached because of it, even above the-allowance. Running the Server Edition has no gate at all, which is a documented, accepted gap.+open; no project, node or tmux session is closed, deleted or detached because of it, even above+the allowance. Running the Server Edition has no gate at all, which is a documented, accepted gap.The reference is `docs/project-limit.md`, in the repo, including the undo runbook.**The check feed can show a one-time popup.** Next to the existing banner messages, e.g. a Pro