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(live-links): what changed in the final fix wave, in the reference, the spec and CLAUDE.md
reviewa92b3f7f7696
diff --git a/CLAUDE.md b/CLAUDE.mdindex 04362a67d..f88b1cc18 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -5674,10 +5674,23 @@ creating one is Pro and the backend is the gate. Reference: **`docs/live-links.mhistory (exact `=nt-<id>:`, no `-S`; session host, plain shell and a Zellij node get no keyframe). Aviewer sizes nothing: `joinOnly` + `sizeVote: false`; its own tmux client is `-E -f ignore-size,read-only`,and a Zellij node never gets one (refused, never a Zellij attach — that client could type).-- Node gone is tri-state (only ABSENT ends a link; a lost or corrupt index is never a complete read).+- Node gone is tri-state (only ABSENT ends a link; a lost or corrupt index is never a complete read —+ `knownNodeIdsStrict()`, which only live links call; the agent-status mirror keeps `knownNodeIds()`,+ which ignores that flag, because a whole-process pause of its pruning was R54's mistake).Link state is never canvas content, no canvas-control verb touches links, the chip is not hideable(`src/renderer/lib/live-link.guard.test.ts`); both shells wire one core service, the Server Edition as`unsupported` until it has a license layer (`src/main/watch-link-wiring.test.ts`).+- `src/shared/watch-link/` is vendored byte for byte into nodeterm-web: siblings and `tweetnacl` only,+ no Node API, type imports spelled `import type` (`isomorphism.guard.test.ts`); a change there owes the+ web repo a re-vendor. Chat text is stripped of controls AND bidi controls there, capped by code point.+- Never silent about what a viewer gets. Where local terminals are not tmux (Windows' session host, tmux+ off or missing, Zellij) a viewer can watch only a terminal the app has OPEN (there is no read-only+ client to spawn): the create dialog says so, and a refused join turns the chip amber `LIVE · 1+ waiting` ("Viewers are waiting — open this terminal in nodeterm…"). The stream is the owner's tmux+ CLIENT's output, so its session chooser or a session switch reaches viewers; the warning names it.+- Stop all is the only control that reaches other machines' links: it is offered to a Pro owner even+ with no link listed here, awaits the server and reports what it reached (`RevokeAllOutcome`) — a+ failed or skipped server call must never look like a stop.## Dev-server ports (the Ports chip + same-port SSH forwarding)diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex cd816e85f..cafbf9fdc 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -509,7 +509,10 @@ anything else. Board-level fields survive every transform — `pullLinks` is oneevent reaches a viewer only once it is added to `watcherEventAllowed`(`src/core/watch-link/watcher-policy.ts`) on purpose — and only if its payload is the visible screen,never history (why `pty:resync` is refused). Never add link state to a node, a board or a canvas op:- canvas sync and the canvas authority would publish it. `docs/live-links.md`.+ canvas sync and the canvas authority would publish it. `src/shared/watch-link/` is copied byte for+ byte into the viewer page's repo: import only siblings and `tweetnacl`, write type imports as+ `import type` (`isomorphism.guard.test.ts` fails otherwise), and expect a change there to need a+ re-vendor. `docs/live-links.md`.- **A change to canvas content that does not travel as a `canvas:mut` op is lost on a hosted core —route new content edits through the op vocabulary (`src/shared/canvas-content.ts`).** On a Serverdiff --git a/docs/live-links.md b/docs/live-links.mdindex bd997483a..a612ffaeb 100644--- a/docs/live-links.md+++ b/docs/live-links.md@@ -34,9 +34,9 @@ link"**, the code says **`watchLink`** (owner IPC, `src/core/watch-link/`), the| Piece | Where | Notes ||---|---|---|-| Keys, URL, wire, protocol, browser client | `src/shared/watch-link/` (`keys.ts`, `link.ts`, `wire.ts`, `protocol.ts`, `client.ts`, `vectors.json`) | Isomorphic: tweetnacl + WebCrypto, no Node API. **nodeterm-web vendors it byte-identically** and runs the same vectors. A protocol change lands here first, with new vectors, then is copied. |+| Keys, URL, wire, protocol, browser client | `src/shared/watch-link/` (`keys.ts`, `link.ts`, `wire.ts`, `protocol.ts`, `client.ts`, `vectors.json`) | Isomorphic: tweetnacl + WebCrypto, no Node API. **nodeterm-web vendors it byte-identically** and runs the same vectors. A protocol change lands here first, with new vectors, then is copied. `isomorphism.guard.test.ts` fails on an import from outside the directory (only siblings and `tweetnacl`), a Node API, or a type imported without `type` (the web repo compiles with `verbatimModuleSyntax`). || Owner types | `src/shared/watch-link-types.ts` | NOT vendored. TTLs, `MAX_LINKS_PER_MACHINE` (5), `LABEL_MAX` (40) / `TITLE_MAX` (80, UTF-16 units), the renderer-facing `WatchLinkApi`, `stripBidiControls`. |-| Registry / service | `src/core/watch-link/service.ts` | Lifecycle, limits, persistence, node-gone, owner state, the ten owner channels (`registerWatchLinkIpc`). Both shells create it. |+| Registry / service | `src/core/watch-link/service.ts` | Lifecycle, limits, persistence, node-gone, owner state, the seven owner request channels (`registerWatchLinkIpc`) and the three owner pushes (state, chat, notice). Both shells create it. || Link host | `src/core/watch-link/link-host.ts` | One hosted scheduler per link, a `connectRelayHost` session per viewer, joins, keyframes, throttling, chat, kick. || Watcher policy | `src/core/watch-link/watcher-policy.ts` | The `RelayHostHooks` of a viewer session: `watcherAccess` (inbound) and `wrapWatcherSink` (outbound). || Output filter | `src/core/watch-link/stream-filter.ts` | Strips string-type escape sequences from the viewer's stream. |@@ -46,7 +46,7 @@ link"**, the code says **`watchLink`** (owner IPC, `src/core/watch-link/`), the| Pty seam | `src/core/watch-link/pty-seam.ts` (`createWatchPty`) | ONE definition of the join rules, both shells wire it. || Store | `src/core/watch-link/store.ts` | `<userData>/watch-links.json`, sealed. || API client | `src/core/watch-link/api.ts` | create / host-token / status / revoke / revoke-all. |-| Existing-code seams | `ui-sink-registry.ts` (`quiet`, `selfPaced`), `pty-reap.ts` (`liveClientIds`), `hosted-scheduler.ts` (`maxBridged`), `host-control.ts` (`watchLink:`), `workspace-store.ts` (`knownNodeIds`, `indexRebuiltThisRun`) | The registry and scheduler options are inert for every caller that passes none. `knownNodeIds()` answering unknown after a rebuilt index is NOT link-only: the agent-status mirror's existence pruning pauses for that run too (R54). |+| Existing-code seams | `ui-sink-registry.ts` (`quiet`, `selfPaced`), `pty-reap.ts` (`liveClientIds`), `hosted-scheduler.ts` (`maxBridged`), `host-control.ts` (`watchLink:`), `workspace-store.ts` (`knownNodeIdsStrict`, `indexRebuiltThisRun`) | The registry and scheduler options are inert for every caller that passes none; a `selfPaced` sink owes the registry a bound on its own backlog, and `maxBridged` must be an integer ≥ 1. Only `knownNodeIdsStrict()` (live links) answers unknown after a rebuilt index: the agent-status mirror keeps calling `knownNodeIds()`, unchanged from before live links (R64/M2; R54 had paused the mirror's pruning for the whole process). || Shell wiring | `src/main/index.ts`, `src/server/index.ts` (search "Live links") | Pinned at source level by `src/main/watch-link-wiring.test.ts`. || Renderer | `state/watchLinks.ts`, `lib/liveLink.ts`, `lib/liveLinkEntry.tsx`, `components/LiveLinkChip.tsx`, `LiveLinkPopover.tsx`, `LiveLinkDialog.tsx`, `settings/sections/LiveLinksSection.tsx` | One chip on four surfaces; availability before the Pro gate. || API | nodeterm-server `watch_links` table + six routes | Merged (server#8). |@@ -98,7 +98,9 @@ Host → viewer: `ev watch:meta {v, role, label, title, expiresAt, cols, rows}`only the first: the page leaves "waiting" on a meta), pty output as binary `encodePtyData` frames,`ev pty:size:<sid>`, `ev watch:keyframe {sessionId, screen, altScreen, cursor?}`, `ev watch:chat`,`ev watch:waiting {}`, `ev watch:end {reason}`. Viewer → host: `cast watch:chat {name, text}`-(Commenter only), `trust:confirm`, keepalives. **There is no input, resize or flow message in the+(Commenter only; `sanitizeChatText` / `sanitizeChatName` bound the raw value by code point before+cleaning, drop C0/C1 controls and the bidi controls, and cap at 500 / 32 UTF-16 units without splitting+a surrogate pair — the same functions the viewer page runs), `trust:confirm`, keepalives. **There is no input, resize or flow message in theprotocol.** `session-ended` is a defined end reason the host never sends in v1: a session that exitsanswers `watch:waiting`, and the host rejoins when one appears.@@ -280,9 +282,9 @@ only client sizes the window like any other (spawned at 40x10 alone → window 4vote, never a viewer's size) before every keyframe capture and every `WATCHER_SIZE_SYNC_MS` (10 s)while the link has a joined viewer; serialized per session in PtyManager (one read in flight, oneshared rerun — R24), so two links on one node share it;-- **residual:** when the watcher becomes the sole client, the window lands on the last-synced size- until another client sizes it — drift for up to one interval, and a read racing an owner's resize or- departure keeps the size read a moment before.+- **residual:** when the watcher becomes the sole client, the window stays at the last-synced size+ until another client sizes it (an owner resize in the last interval before the owner left is not+ caught), and a read racing an owner's resize or departure keeps the size read a moment before.A second viewer shares the watcher client (refcounted by subscribers); the watcher client is unindexed,so every persistKey lookup behaves as "no watcher". An owner attaching with `-D` detaches the watcher's@@ -344,16 +346,19 @@ and resurrect a revoked link at the next boot).the installed app's links).**Node gone is tri-state** (R40, `workspaceNodeState`). Present = some project holds it; absent = the-store has a complete read of every project (`knownNodeIds()`) and the id is not in it; anything else is-unknown. **Only absent** ends a link (`node-gone`, server revoke). An empty answer during the launch-time+store has a complete read of every project (`knownNodeIdsStrict()`) and the id is not in it; anything+else is unknown. **Only absent** ends a link (`node-gone`, server revoke). An empty answer during the launch-timeload, or for a node in a project whose file was not read, is not evidence, and a revoke cannot beundone. The check runs on every workspace load/save (`onWorkspaceChanged`, which also covers a noderemoved by the canvas authority on a peer's op) and before every join (R29). **An index rebuilt fromnothing is never a complete read** (R44, R54, R55): a `workspace.json` that is missing, unreadable,-corrupt, or parses but is no index this build recognises marks the run, and `knownNodeIds()` answers-unknown until the next launch — otherwise the renderer's empty boot save made every node absent and-every link was revoked a second after launch (probe-confirmed). A genuinely empty v2/v3 index is not-flagged.+corrupt, or parses but is no index this build recognises marks the run, and `knownNodeIdsStrict()`+answers unknown until the next launch — otherwise the renderer's empty boot save made every node absent+and every link was revoked a second after launch (probe-confirmed). A genuinely empty v2/v3 index is not+flagged. **The strict accessor is live links' alone** (R64/M2): the agent-status mirror prunes+identities with `knownNodeIds()`, which ignores the flag. A wrongly pruned identity costs one hook event+to restore, while the flag lasts the whole process: a Server Edition started on a fresh data dir runs+for weeks, and under R54's first version the phone kept listing deleted sessions there.**End** (expiry, owner Stop, node gone, server 410): drop the record, ISSUE the write (never awaitedbefore the server revoke — a hung disk must not keep a revoked link's viewers connected or its row@@ -361,7 +366,15 @@ alive), `watch:end` to every viewer, stop the scheduler, emit state, notify (expthe owner's own Stop raises nothing), then the best-effort server revoke. Local revoke is complete evenoffline, because the host is the only listener. **Stop all** is `POST /v1/watch-links/revoke-all`:every link of the LICENSE, other machines included, so both entry points (palette, Settings) confirm-first; it also discards opaque entries (else they would host again once the keychain unlocks).+first; it also discards opaque entries (else they would host again once the keychain unlocks). It is+**offered wherever the owner could have a link to stop** (`showsStopAll`, R62): a link listed here, OR a+Pro license — links shared from another machine are invisible on this one, and Stop all is the only+control that reaches them (a desktop left sharing at the office, a lost laptop whose links resume at+launch); never in the Server Edition. This machine's links stop at once; then the server call is+**awaited** and its answer reported (`RevokeAllOutcome`: `stopped`; `no-entitlement`, the server was not+asked; `failed`; `unsupported`), a success included. The confirm names the timing: this machine's+viewers at once, other machines' links within a few minutes (their next mint, ≤ ~90 s, or a full link's+status poll, ≤ 5 min).**The listener pool.** One hosted scheduler per link with `maxBridged: 10`: at 10 bridged viewers noreplacement listener opens, so the broker closes an 11th client ("no host waiting"). The scheduler's@@ -383,7 +396,8 @@ untouched. A Pro lapse lets open links run out their term (≤ 24 h): host tokenlink row, not keygen.**Hung-disk and quit rules.** Create waits for its write ≤ 10 s; revoke / revoke-all wait for `init()`-only boundedly, so Stop all still reaches the server on a hung disk; `init()`'s own workspace bound fires+only boundedly, so Stop all still reaches the server on a hung disk (its wait for the server's answer+is the API client's 8 s timeout); `init()`'s own workspace bound firesbefore any wait on it, so a slow workspace never reads as a failed write. Desktop: `shutdown()` runs onthe FIRST before-quit pass, before `ptyManager.killAll()`, inside the 1.5 s raced flush — viewers get`host-stopping` while the sockets are up; the records stay on disk and resume at the next launch. Server@@ -400,15 +414,30 @@ carry it to teammates and the canvas authority would write it into the git-share- **Desktop:** full. Entry points: node right-click "Share live link…" (`selectionItems`, shared by thesessions-sidebar row; hideable as `live-link`), the kanban card menu (per-project board AND the Omni- board's lanes, non-active projects included — `joinOnly` attaches in core, so the node need not be on- screen), the card modal header action, the palette ("Manage live links", "Stop all live links (every- machine on this license)"), Settings → Live links (Remote & team). ProCompare lists "Live read-only+ board's lanes, non-active projects included — a viewer of a node with no Session held spawns its own+ read-only tmux client, so on a machine whose local terminals are tmux the node need not be on screen),+ the card modal header action, the palette ("Manage live links", and "Stop all live links (every+ machine on this license)" for a Pro owner or while a link is listed), Settings → Live links (Remote &+ team). Each row is judged by its node's OWN project's session (`liveLinkMenuItemsFor`, D2/M1).+ ProCompare lists "Live read-onlylinks to a terminal — viewers need nothing installed"; the Core list is untouched. **Availability ischecked before the Pro gate** (`liveLinkUnavailable` then `requireProOr`), so a Server Edition or relaytab never sees an Upgrade dialog; an unavailable row is disabled with its reason, never hidden.+- **Desktop where local terminals are not tmux** (Windows' session host; tmux switched off or missing;+ the Zellij backend): there is no watcher client of its own, so a viewer can co-attach only to a+ terminal this app has OPEN (mounted, or parked) — after a restart, for a background project or an+ offscreen-released node, viewers wait. This is said, never silent (R63): the create dialog states it+ before the link exists (`watchableOnlyWhileOpen`, from the local core's `tmuxStatus().persistence`; an+ SSH project's node is served by the host's tmux and gets no note), and while a viewer's join is+ refused the chip turns amber (`LIVE · 1 waiting`) and its title and the popover say "Viewers are+ waiting — open this terminal in nodeterm to let them watch." The fix is a session-host watcher join+ (an additive, negotiated attach-only subscribe with no size vote, beside the visible capture): a+ follow-up.- **The LIVE chip** (`LiveLinkChip`, one component): node header (beside `PresenceChips`), kanban card,card modal header, sessions-sidebar row. `● LIVE`, `● LIVE · 2`, amber `LIVE · offline`- (reconnecting), muted `LIVE · refused`; an unread dot for Commenter chat. **Not hideable** — it is the+ (reconnecting), amber `LIVE · 1 waiting` (a viewer's join was refused — R63), muted `LIVE · refused`;+ an unread dot for Commenter chat. A viewer is reported waiting only once a join is REFUSED: a session+ that merely ends rejoins in seconds and is no news. **Not hideable** — it is theowner's signal that a terminal is being broadcast. It shows only for a node viewed through a LOCALsession (R57): a relay tab's copy of a git-shared node with the same id must not show this machine'schip, and the boards and the sidebar sit outside the node's SessionProvider, so they resolve the@@ -466,11 +495,21 @@ Found while building it:genuinely have no capture, and the flag cannot tell the two apart.- **Frames between a capture and its delivery are dropped for that viewer** (inherent tocapture-then-stream; the next redraw repairs). A keyframe shows the active pane only.-- **Window-size drift** for up to one sync interval when the watcher becomes the sole client (above).+- **Window size when the watcher becomes the sole client**: the window stays at the last-synced size+ until another client sizes it (above).+- **The stream follows the owner's tmux CLIENT, not the node** (R64/M3). A keyframe targets exactly+ `=nt-<id>:`, but the stream is what the owner's client draws: in a shared terminal, tmux's session+ chooser (`C-b s` / `C-b w`, a live preview of every `nt-*` session on the server, other projects'+ agents included) or a session switch (`C-b (` / `)`) reaches every viewer. It is the owner's own+ action, shown on the owner's own screen too, and the create dialog's warning says so. Following+ `#{client_session}` and treating a switch as a lifecycle event is a possible follow-up.+- **Windows, and any machine whose local terminals are not tmux:** a link to a terminal that is not+ open in the app cannot be watched until it is (Surfaces, above). Said, never silent; the session-host+ watcher join is the follow-up.- **A tmux < 3.2 host cannot be watched** (fail closed, "waiting").- **After a run whose index was missing, unreadable or corrupt, node-gone waits for the next launch**(R44/R54): a link to a node deleted in that run lives until its expiry (≤ 24 h) with nobody able to- join it (its session is destroyed), and the agent-status mirror's existence pruning is off that run.+ join it (its session is destroyed). The agent-status mirror is not affected (R64/M2).Likewise a link to a truly deleted node in an unread project lingers until the next complete read.- **Opaque entries** (an unsealable secret) live in the file ≤ 24 h.- **A node cold-opened into a background project** whose disk write has not landed answers@@ -510,6 +549,14 @@ From the spec:15. **A viewer stays connected for more than 2 minutes without a drop** — whether production ends abridged socket at its token's lifetime is unverified (the same open question as hosted checklistitem 8).+16. **Windows:** create a link to a background project's node (or relaunch with a link resumed): the+ create dialog says "only while it is open", a viewer waits, the owner's chip reads `LIVE · 1+ waiting` with the waiting sentence; opening the terminal lets the viewer watch.+17. **`C-b s` / `C-b w` in a shared terminal:** the viewer sees the chooser's previews of other+ sessions, exactly as the owner does (the create dialog's warning names it).+18. **Stop all from a second machine with no link listed:** the palette and Settings offer it to a Pro+ owner; the first machine's links end within a few minutes; with the network cut, the stop says it+ did not reach nodeterm.Added while building it:diff --git a/docs/superpowers/specs/2026-09-28-live-share-link-design.md b/docs/superpowers/specs/2026-09-28-live-share-link-design.mdindex f91b29e23..25931e051 100644--- a/docs/superpowers/specs/2026-09-28-live-share-link-design.md+++ b/docs/superpowers/specs/2026-09-28-live-share-link-design.md@@ -219,8 +219,9 @@ protocol.**listener.- **Node gone:** on every workspace-store change and before every join, the registry asks whetherthe node is `present`, `absent` or `unknown`: present = some project holds it- (`projectIdsForNode`); absent = the store has a complete read of every project (`knownNodeIds()`)- and the id is not in it; anything else is unknown. Only **absent** ends the link with `node-gone`+ (`projectIdsForNode`); absent = the store has a complete read of every project+ (`knownNodeIdsStrict()` — unknown, too, for the rest of a run whose index was rebuilt from nothing;+ the agent-status mirror keeps `knownNodeIds()`, which does not read that flag) and the id is not in it; anything else is unknown. Only **absent** ends the link with `node-gone`and revokes it server-side — an empty answer during the launch-time workspace load, or for a nodein an unreadable project, is not evidence the node is gone. Create requires `present`. This coversa node removed by the canvas authority on a peer's op, which the local renderer's delete funnel@@ -451,7 +452,12 @@ server is the gate.- **Card modal header:** a "Share live link" action on terminal cards.- **Command palette:** "Manage live links" (opens the Settings section) and "Stop all live links(every machine on this license)". Stop all revokes every link of the license, other machines- included, so both entry points (palette and Settings) confirm first.+ included, so both entry points (palette and Settings) confirm first. It is offered wherever the owner+ could have a link to stop — a link listed on this machine, OR a Pro license (links shared from another+ machine are invisible here, and Stop all is the only control that reaches them) — never in the Server+ Edition. The confirm names the timing ("Viewers on this machine are disconnected at once; links on+ other machines stop within a few minutes"), and what the server call reached is always reported:+ stopped, could not be asked (no entitlement here), or did not reach nodeterm.- **Disabled with a reason, never hidden:**- relay-tab node: "Live links are created on the machine that runs this terminal."- Server Edition tab: the R43 sentence ("Live links need a Pro license on this server — not@@ -459,8 +465,13 @@ server is the gate.- unpackaged build (`relayAllowed()` false): "Live links need the installed app." — shown whenCreate is pressed (the renderer has no `relayAllowed` probe; a dev-build-only case).- 5 active links: "Stop a live link first — 5 can be active at once."-- Creating a link does not need the node on screen (`joinOnly` attaches in core), so the Omni- board's cards of other projects can create links too.+- Creating a link does not need the node on screen, so the Omni board's cards of other projects can+ create links too. Watching one does — on a machine whose local terminals are not tmux: with no Session+ held, a viewer spawns its own read-only TMUX client, which Windows' session host, a machine with tmux+ off or missing, and the Zellij backend do not have. There a viewer can co-attach only to a terminal+ the app has open, and the owner is told (below: the create dialog's note, the chip's waiting state).+ A session-host watcher join (an additive, negotiated attach-only subscribe with no size vote, beside+ the visible capture) is the follow-up.### Create dialog@@ -469,10 +480,14 @@ server is the gate.- Expiry: 15 min / **1 hour** / 8 hours / 24 hours.- "Shown to viewers as": prefilled with the presence name, ≤ 40 chars.- An always-visible warning: "Anyone with the link sees everything this terminal shows: what's on- screen now, anything printed later (tokens, env dumps), and anything you scroll back to. They- can't type or resize it."-- "Create live link" → the URL with **Copy**, "Anyone with this link can watch until 15:42", and- **Stop sharing**.+ screen now, anything printed later (tokens, env dumps), anything you scroll back to — and, if you+ open tmux's session chooser or switch sessions in it, those other sessions too. They can't type or+ resize it." (The stream is the terminal CLIENT's output, not the node's; see the residuals.)+- On a machine whose local terminals are not tmux, for a node that is not an SSH project's: "On this+ machine, viewers can watch this terminal only while it is open in nodeterm; otherwise they wait until+ you open it." An unread status claims nothing.+- "Create live link" → the URL with **Copy**, "Anyone with this link can watch until 15:42" ("until+ tomorrow 15:42", or the weekday and date, when it ends on another day), and **Stop sharing**.- Errors: 402 → "Live links need an active Pro plan." + Upgrade; 429 → which limit; network →"Couldn't reach nodeterm's service. Nothing was shared."@@ -481,6 +496,8 @@ server is the gate.Node header (beside `PresenceChips`), kanban card, card modal header, sessions sidebar row.- `● LIVE` (a link, no viewers), `● LIVE · 2` (watchers), amber `LIVE · offline` (reconnecting),+ amber `LIVE · 1 waiting` (a connected viewer whose join was refused — no session it may join; the+ title and the popover say "Viewers are waiting — open this terminal in nodeterm to let them watch"),muted `LIVE · refused` (the API refuses mints). A dot marks unread Commenter chat.- **Not hideable.** It is the owner's signal that a terminal is being broadcast; it is not in`HIDEABLE_HEADER_BUTTONS`, pinned by a guard test.@@ -494,8 +511,9 @@ Node header (beside `PresenceChips`), kanban card, card modal header, sessions s### Settings → "Live links"-Every active link (node, project, role, viewers, remaining time, Copy, Stop) and "Stop all". Non-Pro-users see a short pitch and Upgrade.+Every active link (node, project, role, viewers, remaining time, Copy, Stop) and "Stop all" (also for+a Pro owner with no link listed here — it reaches the other machines' links). Non-Pro users with no link+see a short pitch and Upgrade.### ProCompare@@ -556,6 +574,11 @@ only calls `requireProOr`, which today has zero callers.)- **Residual — the owner-supplied label and node title are shown to viewers.** They are rendered astext inside fixed nodeterm chrome, marked as sharer-set; terminal output cannot draw over thechrome and has no clickable links.+- **Residual — the stream follows the owner's tmux client, not the node.** A keyframe targets exactly+ `=nt-<id>:`, but a co-attached viewer receives what the owner's client draws: tmux's session chooser+ (`C-b s` / `C-b w`, a live preview of every `nt-*` session on the server) or a session switch shows+ other sessions to every viewer. It is the owner's own action, on the owner's screen too, and the+ create dialog's warning names it.## Testing