4 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude Opus 4.7	6c5c67f6dc	add a clide-hosted team coordination broker over the MCP control channel ... Claude's tmux team mode let teammates message each other and share a task list; that mode is undocumented and unavailable headless. clide rebuilds the same behavior over its own managed sessions, as the broker. Verified live against claude 2.1.150 that a spawner can host an in-process ("SDK") MCP server entirely over the stream-json control channel — no subprocess, no --mcp-config, no socket: declare the server name in the initialize handshake's sdkMcpServers, answer the mcp_message JSON-RPC round-trips (initialize / tools/list / tools/call) under response.response.mcp_response. SDK tool calls are permission-gated through the existing can_use_tool path. Documented in the 2.1.150 spike §6. StreamJsonSession gains an McpServer hosting seam; TeamBroker + TeamMcpServer expose send_message / broadcast / list_teammates / inbox / claim_task / task_status, all routed through one shared broker. The orchestrator owns the broker, registers each team session, delivers a message into the target's next turn on its stdin, and injects roster + role via --append-system-prompt. Solo sessions are unchanged (no MCP server, no initialize handshake). T-170, D-77. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 21:37:53 +02:00
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	8310730506	document the stream-json control protocol + D-78 ... Empirical spike against claude 2.1.150 (driving the real CLI over stdin/stdout + reading the shipped binary's zod schemas) pinned the wire shapes for the stream-json control protocol: the can_use_tool permission request, the control_response envelope, the --permission-prompt-tool stdio enabler (without it "ask" tools silently auto-deny), the allow-requires-updatedInput quirk, and AskUserQuestion answered via updatedInput.answers. Captured in a version-pinned spike note with a resilience section (detection canaries + a ranked fallback menu) so a future Anthropic change to this undocumented contract doesn't leave us at a blank slate. D-78 records the decision: permissions ride the stdio control channel, not MCP (MCP is reserved for capability/tool provision); refines D-77. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 08:40:05 +02:00
jpmschweitzerandClaude	3f2e5ad9a9	spike T-134: Claude Code team/transcript internals (pinned to 2.1.148) ... Findings note for the tmux agent-team work (epic T-132), validated from real on-disk artifacts (42 past team configs, real team + subagent transcripts, current-version .meta.json) plus a synthetic control-mode test and the tmux manual — no live team run / quota needed. Key results: teammates get tmux panes (config tmuxPaneId) and write transcripts at <munged>/<sid>/subagents/agent-<hex>.jsonl + .meta.json; tmux 3.6a has no %pane-died (use %window-close/%layout-change), and polling list-panes -a is the reliable lifecycle baseline; the real risk is identity linkage — pane/teammate (config: name@team, agentType, %pane) joins to the transcript only via agentType (config <-> .meta.json), ambiguous for same-type teammates, so T-139 needs a joinedAt/mtime or lead-transcript tiebreaker. Co-Authored-By: Claude <noreply@anthropic.com>	2026-05-22 19:52:00 +02:00