Drop in to a stuck agent from the board #196

Activity

1. barelyworkingcode

   added

   enhancementNew feature or requestNew feature or request

   needs-reviewAwaiting owner reviewAwaiting owner review

   on Oct 6, 2026
2. barelyworkingcode

   added a parent issue on Oct 6, 2026

   • Agent attention and Chief of Staff relay#231
3. barelyworkingcode

   marked this as blocked by 2 issues on Oct 6, 2026

   • Show which agents need me on the agent board #195
   • Take over a headless Claude session in a terminal relay#233
4. barelyworkingcode

   removed

   needs-reviewAwaiting owner reviewAwaiting owner review

   on Oct 6, 2026
5. barelyworkingcode commented on Oct 6, 2026

   

   barelyworkingcode

   on Oct 6, 2026

   OwnerAuthor

   More actions

   Approved by the owner on 2026-10-05: the whole epic (relay#231 and its seven children). needs-review removed.
6. barelyworkingcode commented on Oct 6, 2026

   

   barelyworkingcode

   on Oct 6, 2026

   OwnerAuthor

   More actions

   Contract (eve#196)

   The relay side is pinned to relay PR #239 at head 4c956a5 (feat/233-drop-in-2), which is not merged yet. Until it merges, the new source pins run with EVE_RELAY_SOURCE set to a worktree of that head.

   Open question (sent to the coordinator)

   Q1: relay refuses drop-in on non-headless sessions (409 not_headless). eve's list rows carry model but no headless field. Recommended: relay adds headless to Summary, and eve shows Drop in only on headless Claude rows. Until that is decided, the predicate lives in one place, AgentBoard.showsDropIn.

   Decisions made for the owner

   1. A browser HTTP route, POST /api/sessions/:id/drop-in, in routes/index.js. It goes through the existing proxy(), and so through RelayTransport. It is not a WS frame, because the dispatcher's shared error path writes into the chat pane.
   2. "Claude" uses relay's own rule: the model is haiku, sonnet or opus (deriveSessionKind). This is pinned against relay. pi/…, codex/… and all other models show no action.
   3. Closing the tab ends the terminal through the existing WS terminal_close. At 4c956a5, relay's handleTerminalClose calls mgr.Close, the same as DELETE /api/terminals/{id}. Relay then calls HandBack. This is pinned. There is no new DELETE call.
   4. The terminal opens through the existing path: onTerminalCreated and then join_terminal, at a size of 80×24, as createTerminal does.
   5. No client timeout. Relay bounds the wait to 60 s plus the launch. Aborting sooner would orphan a launched terminal.
   6. A refusal shows relay's message verbatim as a toast (EVT.TOAST_SHOW). When eve can't reach relay, the toast falls back to "relay isn't reachable".
   7. The route requires a JSON {cols, rows} body, with each value a whole number from 1 to 500. A cross-site no-cors POST can't send that body.

   Doors

   • Simple: Today → Agents → Needs you → Drop in. The project page's Agents section has the same action.
   • Power: relay drop-in <session-id> (relay#233). eve adds no config.

   Wire

   Browser → eve: POST /api/sessions/:id/drop-in with {"cols":80,"rows":24}.

   • A bad body gets 400, and eve does not call relay.
   • Otherwise eve returns relay's status and body unchanged: 201 {sessionId, claudeSessionId, host?, terminal}, or a refusal {error, message}.

   File ownership

   Task	Files
   D1 dev	public/agent-board.js, public/terminal-manager.js (add openDropIn only), public/core/api-client.js (dropIn), routes/index.js (CRLF), public/apple/agents.css, docs/FEATURES.md, docs/api.md, docs/design-workbench.md
   T1 tests	test/unit/agent-board.test.js (add only), test/unit/drop-in-route.test.js, test/unit/terminal-drop-in.test.js, test/integration/fake-relay.js, test/integration/relay-source-pins.test.js, test/integration/relay-fidelity.test.js, test/e2e/goals/agent-drop-in.spec.js, docs/baseline.md
   T2 harness	devboxverify/journeys.js, devboxverify/README.md, test/unit/devboxverify.test.js (additive only)

   Proof plan

   • Playwright goals/agent-drop-in: "Drop in opens a terminal"; a refusal shows relay's reason; pi/ and codex/ rows show no action.
   • devbox journey agent-drop-in: a real headless Haiku agent; a fault injected mid-turn leaves it errored; Drop in opens a terminal on the same conversation; closing the tab brings back idle.
   • SSH-host drop-in: needs a test-machine pass.
   • Break-and-restore: remove the join_terminal send in openDropIn.
7. barelyworkingcode

   added 2 commits that reference this issue on Oct 6, 2026

   fix: agent-drop-in finds claude through the relay-sessions shim (#196)

   ...

   3e9f98f

   fix: review round 2 (#196)

   ...

   70e1492
8. barelyworkingcode commented on Oct 6, 2026

   

   barelyworkingcode

   on Oct 6, 2026

   OwnerAuthor

   More actions

   State 2026-10-06 01:02 PDT: ready, waiting on relay#239

   PR #203 (head 70e1492) meets every merge-check condition except its dependency.

   • CI green; devbox/verify success (34/0).
   • Review round 3: no blocking findings.
   • Real-app check, journey, main-harness-vs-head and break-and-restore lines are in the PR.

   Waiting on: relay#239 (drop-in), held for the owner, item 3 (cmd/relay/api_credential.go). relay#241 (headless on the list) is already on relay main.

   To merge after relay#239 lands:

   1. Rebuild Relay.app from relay main and restart eve-verify.
   2. Re-run set.js --eve 203 --post if the head moved or relay changed since 70e1492.
   3. Run the relay pins against relay main (they now hold the drop-in route).
   4. Run merge-check.

   Not covered: SSH-host drop-in needs a test-machine pass.
9. barelyworkingcode

   added a commit that references this issue on Oct 6, 2026

   Merge pull request #203 from barelyworkingcode/feat/196-drop-in

   ...

   e34a1ea
10. barelyworkingcode

    closed this as completedin #203on Oct 6, 2026