Skip to content

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.

docs(release): add the Simulator node and bulk pause to the v0.4.4 highlights

reviewc9c560d0d06a
diff --git a/docs/release-notes/v0.4.4.md b/docs/release-notes/v0.4.4.md
index 9c05a448d..11b834e74 100644
--- a/docs/release-notes/v0.4.4.md
+++ b/docs/release-notes/v0.4.4.md
@@ -8,6 +8,34 @@ update itself: it checks for new versions and shows a card that links to the dow
the new installer over the old one. Your projects and settings are kept, and on 0.4.1+ your running
sessions survive the update. Signing is the next phase.
+**A simulator is a node now.** iOS simulator and Android emulator screens live on the canvas:
+click to tap, drag or scroll to swipe, type straight into the device, Home and Lock buttons, and a
+device picker that boots one. It is a real stream rather than a screenshot — nothing is encoded
+while the screen sits still, about 19–30 fps while it moves, first frame in roughly 0.4 s. A run
+node gets a phone button that opens its device inline under the run controls, so a Flutter or React
+Native run and the screen it produces are one node; you can pop that screen out into a node of its
+own and dock it back. The overflow menu mirrors DeviceHub's own: appearance, text size, location,
+status-bar overrides, shake, Face ID, Open URL, push notifications, installs, screenshots — and
+what cannot be driven from outside is listed greyed out with the reason instead of quietly
+missing. iOS needs macOS and Xcode (the node draws the device through a small Swift helper it
+compiles on first use, about three seconds, once per Xcode build); Android virtual devices work on
+every desktop OS, Windows included, over the emulator's own interface. Desktop only — a browser or
+relay tab says so rather than showing an empty frame.
+
+**You can pause a whole project, including the sessions you cannot see.** The project menu pauses
+every agent in a project, a group frame pauses the ones inside it, and a selection of two or more
+pauses just those; the tab carries a count while they are down, and Resume all brings them back.
+The sessions that are not on screen are the point — a project you are not looking at has no
+terminal mounted, and those are exactly the ones holding a few hundred megabytes each. Nothing is
+interrupted: a session mid-turn, or sitting on a question, is marked and pauses the moment its turn
+ends cleanly, and Cancel pending pauses drops those marks. A pause exits the agent CLI only; the
+session, your shell and your scrollback stay, and resuming continues the conversation where it
+stopped. It also tells you the truth about every session it touched — paused, pausing when the turn
+ends, unreachable, not eligible, skipped and why — so a batch against a disconnected host never
+reports a silent zero. Right after an app restart only a session last seen idle is paused and the
+rest are skipped rather than guessed at, because at that moment an idle CLI and one mid-turn look
+identical. SSH projects included.
+
**Updates stop nagging, and Restart finally says something.** This is the part macOS users will
notice. Clicking **Restart to update** used to look like nothing had happened while macOS staged
the update underneath; now the button shows Preparing… and Restarting… and the canvas is saved