Repository navigation
docs(rfc): remote crews in the chat sidebar and session ownership - #16489
Conversation
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Wave 1 closes #10618 and #14585 as superseded, so relayed peer approvals stay unanswerable until wave 3 ships. A maintainer accepting the RFC should confirm that gap is acceptable. [DESIGN-REVIEWED] f52f672 Description read[DESCRIPTION-READ] f2f4b8e9a6112ab98bb3152caa6616ace0bb3151ef39454d5cc4edce0977efb0 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
…session ownership Proposes per-machine sidebar groups (Local + one collapsible group per connected crew with a connection badge, cached-and-dimmed when disconnected) and peer-owned crew sessions viewed through the existing api/chat + api/stream proxy, retiring the relay-into-local-slot model in waves. Adds the index row.
|
|
|
|
|
|
|
8626cf6 to
f52f672
Compare
Record maintainer iamwhatever's acceptance of the remote-crew sidebar RFC (option (b): the peer owns a crew session and the local dashboard is only a window, plus per-machine sidebar groups). Status moves from draft to accepted, doc-pr names #16489, the prose status line and the directory README row say so, and the decision is written under the document's Open questions with its date. Nothing is implemented on main.
Record maintainer iamwhatever's acceptance of the remote-crew sidebar RFC (option (b): the peer owns a crew session and the local dashboard is only a window, plus per-machine sidebar groups). Status moves from draft to accepted, doc-pr names #16489, the prose status line and the directory README row say so, and the decision is written under the document's Open questions with its date. Nothing is implemented on main. Co-authored-by: Joe Guo <zejiangg@amazon.com>
Problem / Motivation
Goal: Put one draft decision on record for how connected crews appear in the chat sidebar and which machine owns a chat on a crew, so the follow-up sidebar and ownership work has a design to trace to.
Today the sidebar mixes local and peer sessions in one list, told apart by a badge. A "chat on crew" is a local slot whose turns are relayed to the peer, so one conversation has two transcripts. That split is behind several open defects: peer approvals nobody can answer (#10618), a live peer turn shown as "Turn interrupted" after a hub restart (#14585), continue/regenerate/rewind refused with 409, the executor lost on one restore path (#10826), hub-side parent rewriting for peer workers (#14907), and older peer sessions you cannot browse (#7445).
Why it matters
Each defect is being fixed one at a time by adding another mirror of peer state onto the local slot. Without a decision on ownership, every fix grows the relay further. The sidebar shape depends on the same decision.
Not a goal
executor: 'remote'subagent placement (feat(subagents): add remote executor placement #12821).draft; a maintainer records acceptance.What changed (motivation → approach → change)
The two transcripts cause most of the remote-chat bugs, so the RFC compares keeping them (a) with letting the crew own its session and showing it through a window (b). Option (b) wins: every action it needs already exists on the crew's chat API, which the hub can already reach. The RFC also proposes grouping the sidebar by machine, with a connection badge per crew and dimmed cached rows when a crew is offline. It lays out five follow-up waves and five open questions, including what a crew chat shows for project and workspace. The RFC index gets one row and one preamble line for it.
Backwards compatibility
Compatible: documentation only; no runtime behaviour changes.
Removes nothing: the diff adds one document and one index row.
Tests
N/A — documentation only.
python3 scripts/docs_lint.pypasses locally (index reachability and citations).Manual verification
Every cited symbol and path was checked on main at
e698e8ca7a:remote_bound_refusaland its four callers,relay_remote_turn's KNOWN GAP note,_apply_recent_session(no executor restore),_clean_peer_parent,_PROXY_ALLOWED_PREFIXES, the approve/continue/regenerate/rewind routes underapi/chat, andTunnelState.Related Issues
Refs #6180, #7445, #10618, #10826, #14585, #14907
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)