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
Merge pull request #865 from eneskirca/fix/triage-827-811-20260923
eneskircaa6cf9c1befaa
diff --cc CLAUDE.mdindex 22f56a100,f78031809..55aea8eb9--- a/CLAUDE.md+++ b/CLAUDE.md@@@ -569,17 -569,13 +569,13 @@@ Lifecycle, by intentlanded. The predicate is deliberately the narrowest one that closes it — a tmux-backed session isnever protected (the kill costs a redraw), and neither is a plain terminal, a finished agent oran unknown state (nothing is running to lose). **A fifth lever owes the same gate.**- The fifth is the offscreen release of an ARMED node (`--after`, `shouldDeferReleaseForHeldLaunch`,- 2026-09-02): the held launch is delivered by session NAME, so with tmux underneath the release is- harmless and the node stays `sessionReady` (the teardown keeps the flag for an offscreen release- of a tmux-backed session); on the plain-shell fallback the release would destroy the very pane- the launch is typed into, so it is deferred while armed. MEASURED before the fix: a released- QUEUED node held its launch through its dependency going `done`, the badge claimed the terminal- "has not started yet", and only a camera travel (revive) ever fired it — "the chain works when I- look at it" was this.+ The fifth is the offscreen release of an ARMED node (`shouldDeferReleaseForHeldLaunch`):+ held launches now require the attached transport for echo verification, on every backend.+ Keep that transport until delivery or recovery; a blind paste by session name loses the+ shell-init repair and canonical-line protections.- **Node unmount (project switch)** → the RENDERER **parks** the terminal (`TerminalNode.tsx``parkedTerminals`): the xterm instance + its attached PTY stay alive with the `.xterm` element- detached from the DOM, so a remount within `TERM_PARK_MS` (5 min) re-adopts them — instant, and+ detached from the DOM, so a remount within the park window re-adopts them — instant, andexact (the tmux client never detaches, so mouse-tracking/alternate-screen modes and scrollbackcarry over; do NOT "optimize" this into a respawn+redraw — a fresh xterm on a reused clientmisses the attach-time mode sequences and breaks scrolling). The park timer then runs the real