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: correct three statements about the offline relay session and a relay limit

review90f7a7c10f0d
diff --git a/CLAUDE.md b/CLAUDE.md
index 0a44199af..68c193332 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -626,9 +626,10 @@ project's nodes only.** The contract:
`sshRemoteTmux` onto them — the host's core would then refuse its own sessions (`requireRemote`
with no master of its own: `held-elsewhere` for a live one, a refused spawn otherwise). Three
layers besides the keying above:
- (1) `sessionForProject` resolves a REMOTE project (`remote` in the store, or bound while remote in
- this run) with no live binding to the OFFLINE relay session (`OFFLINE_RELAY_SESSION_ID`,
- `session/offline-relay-session.ts`: `source 'relay'`, `status 'offline'`), never the local one.
+ (1) `sessionForProject` resolves a REMOTE project (`remote` in the store; once the store no longer
+ holds it, bound while remote in this run) with no live binding to the OFFLINE relay session
+ (`OFFLINE_RELAY_SESSION_ID`, `session/offline-relay-session.ts`: `source 'relay'`, `status
+ 'offline'`), never the local one.
Its core-bound calls (pty, fs, git, workspace, …) reject, so no terminal can be created here; it
is not a wall around this machine, since its api spreads `...local` like a live relay tab's (the
local namespaces — contextLink, transcripts, handoff, media — still act here, and its `boardLog`
@@ -10080,8 +10081,9 @@ under one `$HOME`, with different bytes; the last writer wins.
`context:update` metadata (deploy one core per team); a viewer's socket backlog over 1 MB still
pauses the shared pty through Stage 2 backpressure; the canvas authority's own limits (a project's
non-content fields stay last writer wins between tabs, the share-time window, oversized nodes, board
-edits to another core, load-time repairs that are never cast, the GitHub issue summary modal's
-"Agent runs" log on a relay tab) are under "Known limits" in the doc.
+edits to another core, load-time repairs that are never cast) are under "Known limits" in the doc;
+the GitHub issue summary modal reading its "Agent runs" log from this machine on a relay tab is under
+"Limitations (v1)".
**Surfaces:** Desktop is full (joiner, plus approval and invite code in an owner's hosted tab, plus
Share with team from any desktop OS onto a Linux host). Server Edition is the host (the `team` CLI,
diff --git a/docs/hosted-team-relay.md b/docs/hosted-team-relay.md
index c8edf8c03..3d65d85cb 100644
--- a/docs/hosted-team-relay.md
+++ b/docs/hosted-team-relay.md
@@ -798,11 +798,6 @@ it is a new way to use it.
client's baseline and is never cast, so on a governed project it never reaches disk: every load
derives it again. The repairs are deterministic, so this costs nothing visible, but a repair that
must persist on a shared project has to be cast.
-- **The issue summary modal's "Agent runs" on a relay tab** (`GitHubIssueSummaryModal` →
- `BoardLogPanel`) still pairs the LOCAL api with the relay project's id: `KanbanView` renders under
- App's local provider, and unlike the card modal this modal is not wrapped in
- `ProjectSessionScope`, so the history is read from this machine's core, not the host's. It is
- pre-existing; a follow-up.
## Status and troubleshooting
@@ -1174,6 +1169,11 @@ are unchanged.
leaves. Past 8 MB its output is dropped (redrawn later) and the pause is handed back
(`ui-sink-registry.ts`).
- **Shared canvas edits:** see [Known limits](#known-limits) under Shared canvas authority.
+- **The issue summary modal's "Agent runs" on a relay tab** (`GitHubIssueSummaryModal` →
+ `BoardLogPanel`) still pairs the LOCAL api with the relay project's id: `KanbanView` renders under
+ App's local provider, and unlike the card modal this modal is not wrapped in
+ `ProjectSessionScope`, so the history is read from this machine's core, not the host's. It is
+ pre-existing; a follow-up.
- **No git for Viewers in a subfolder of a larger repository.** Viewers and Commenters get the git
panel only for a project that is the top folder of its own repository (or a worktree's). A
monorepo subfolder shows its files but refuses every git read (see [Roles](#roles)).
diff --git a/src/renderer/canvas/Canvas.tsx b/src/renderer/canvas/Canvas.tsx
index e52601d1b..bcfc1ec02 100644
--- a/src/renderer/canvas/Canvas.tsx
+++ b/src/renderer/canvas/Canvas.tsx
@@ -5663,7 +5663,10 @@ export function Canvas() {
// The fresh session is now bound to the tab (openRelayTab rebound the SAME project id),
// so it is finally safe to drop the stale offline session it replaced. Disposing only
// AFTER a successful rebind is what keeps a FAILED reconnect reconnectable: if approval
- // never lands, the offline session stays bound and the tab stays greyed-clickable.
+ // never lands, the stale session stays bound, so the next attempt still finds it
+ // (`boundSessionForProject` in reconnectRelay) and a hosted remount still finds the tabs
+ // it served (`projectIdsBoundToSession` in placeProjects). The tab stays greyed either
+ // way: an unbound remote tab resolves to the offline relay session.
if (staleSessionId) {
disposeSession(staleSessionId)
if (hosted) useHostedTeams.getState().forget(staleSessionId)