Dashboard: Send instructions to running agent from browser #354

New issue

Open

opened 2026-04-15 08:44:39 +00:00 by mprihoda · 1 comment

mprihoda commented

2026-04-15 08:44:39 +00:00

(Migrated from github.com)

Layer: 3 — Agent Integration
Parent: #343

Problem

When an agent finishes and needs input, you currently have to switch to the tmux session to respond. With 9-10 concurrent worktrees, this context switching is the primary workflow bottleneck.

Solution

Input field in transcript viewer — type a response/instruction and send it to the running Claude Code session
Use claude-code-query Session API — session.send(prompt) to send input, session.stream() to receive responses
SSE streaming for real-time response display (same pattern as procedures project chat)
Session lifecycle — handle cases where the session has ended (offer to start a new one) or is mid-turn (queue the input)

Architecture

Dashboard server manages Claude Code sessions via claude-code-query library
Browser ↔ Server communication via SSE (server-sent events) for streaming responses
Server ↔ Claude Code communication via the Session trait (send/stream)
Sessions survive browser tab close (server-side process management)

Dependencies

works.iterative:claude-code-query-direct_3 (or effectful) for session management
Transcript viewer (#353) for display

**Layer:** 3 — Agent Integration **Parent:** #343 ## Problem When an agent finishes and needs input, you currently have to switch to the tmux session to respond. With 9-10 concurrent worktrees, this context switching is the primary workflow bottleneck. ## Solution 1. **Input field in transcript viewer** — type a response/instruction and send it to the running Claude Code session 2. **Use claude-code-query Session API** — `session.send(prompt)` to send input, `session.stream()` to receive responses 3. **SSE streaming** for real-time response display (same pattern as procedures project chat) 4. **Session lifecycle** — handle cases where the session has ended (offer to start a new one) or is mid-turn (queue the input) ## Architecture - Dashboard server manages Claude Code sessions via `claude-code-query` library - Browser ↔ Server communication via SSE (server-sent events) for streaming responses - Server ↔ Claude Code communication via the Session trait (send/stream) - Sessions survive browser tab close (server-side process management) ## Dependencies - `works.iterative:claude-code-query-direct_3` (or effectful) for session management - Transcript viewer (#353) for display

claude referenced this issue

2026-10-16 04:45:24 +00:00

Dashboard: Browser-based agent sessions with SSE streaming #355

claude commented

2026-10-16 04:48:14 +00:00

Member

Intake: needs-human
Workflow: -
Reason: G8 waits for issue #353 (transcript viewer), which is open; the input field of this issue goes into that viewer (seen before the analysis)
Analysis: - (no branch, no worktree)

Intake: needs-human Workflow: - Reason: G8 waits for issue #353 (transcript viewer), which is open; the input field of this issue goes into that viewer (seen before the analysis) Analysis: - (no branch, no worktree)

claude added the

needs-human

label

2026-10-16 04:48:15 +00:00

claude referenced this issue

2026-10-16 08:57:18 +00:00

Redesign worktree card for clearer next actions #118