4 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude Opus 4.7	2243237b13	refine the prompt/log UX: show commands, de-emphasize injects ... Two spot-check fixes (T-178, T-179), both grounded in a boundary test of the stream-json wire (findings folded into the spike doc): - Harness-injected user messages (skill loads, slash-command expansions, system reminders) carry isSynthetic on the wire (isMeta in the transcript). They were rendering as blue "you" cards though the user never typed them; now UserMessage.injected flags them and the view shows a muted, collapsed "context" card instead. - Permission prompts now show the command/input being permitted (a capped, scrollable code block) so you can see what you approve. Instead of fully hiding a prompted tool-use, once resolved it collapses to a one-line summary with a green (approved) or red (denied) border; the session tracks per-tool_use_id outcome and the view colours it. The result is kept. Corrects an earlier wrong assumption: the Skill tool is auto-allowed (no permission prompt); the inject only appears once the Skill tool is actually invoked, which is why deny-captures missed it. T-178, T-179, D-78. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 10:26:33 +02:00
jpmschweitzerandClaude Opus 4.7	de264e7141	flesh out the Claude prompt UX: options, stepper, collapse ... Builds on the in-composer prompt surface (D-78): - Permission prompts (T-175): Allow / Allow-and-don't-ask-again / Deny. "Don't ask again" appears only when the request carries a permission_suggestion and echoes it back as updatedPermissions. An optional note rides Deny as the message, or Allow as a follow-up user message (the protocol has no allow-with-message). - AskUserQuestion picker (T-176): a single question renders bare; 2-4 questions step one at a time (nav shows "N · Header", ✓ when answered) then a review/confirm screen. Each question offers an "Other" free-text choice and a per-choice note; multi-select joins labels. A "chat instead" escape denies the prompt so the user can type freely. On submit the answer is echoed into the log, since the card is ephemeral. - Collapsed tool cards (T-177): multi-line tool_use / tool_result start collapsed behind a one-line summary; one-line output renders inline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 09:30:50 +02:00
jpmschweitzerandClaude Opus 4.7	39f9ed018c	drive the Claude pane over stream-json with native prompts ... Replaces the Claude pane's tmux-TUI + transcript-tail backend with Claude Code's stream-json control protocol (D-77/D-78). A StreamJsonSession owns the `claude` process: its event stream feeds the existing ConversationController, and permission / AskUserQuestion prompts arrive as can_use_tool control_requests. Those surface as a ToolPrompt in the composer zone — the pane swaps the text input for an Allow/Deny card or an option picker while a prompt is open, so interaction stays out of the conversation stream and the prompt buttons don't fight the message-card hover chrome. The decision is written back as a control_response (allow echoes updatedInput; AskUserQuestion answers go in updatedInput.answers). Unsupported control subtypes are answered with an error so a turn never hangs. Session continuity is --resume (existing transcript) vs --session-id (new); /clear and /resume respawn the process. The transcript reader still backs the sidebar/status/team surfaces. T-165, T-166. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 08:40:18 +02:00
jpmschweitzerandClaude Opus 4.7	1e77d72361	add StreamJsonSession transport (T-165 foundation) ... The testable core of the stream-json pivot (D-77): StreamJsonSession drives a claude process in stream-json mode — parsing its line-delimited events into the existing ConversationItem / SessionStatus types (reusing parseTranscriptChunk, since stream-json assistant/user events share the transcript's message.content shapes), pulling permission-mode off the init event, and sending user input as stream-json over stdin (with a local echo so the user's own message renders immediately). The process is abstracted behind StreamJsonProcess so it unit-tests without spawning; the real ClaudeStreamJsonProcess wraps Process.start. Not yet wired into the pane — the claude_pane integration (replace the tmux/PTY spawn + TranscriptReader feed, route input through send) and live verification are the next step. T-165. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-24 18:41:34 +02:00