Problem
chat.ts opens every ACP session with mcpServers: []. Integrated agents get no SproutGit tools at all — an agent that wants to create a worktree, check PR state, or fan out subtasks has to shell out to raw git/gh and hope for the best. All the agent-facing capability we're building (#137 fan-out, #138 PR lifecycle, #135 base-aware worktree creation) would otherwise only be reachable by humans.
Proposal
This is the piece that makes the orchestration epic agent-agnostic: any ACP-speaking agent — including ad-hoc ones from the roster issue — gets the same tools as the built-in presets, with zero per-agent integration work.
Problem
chat.tsopens every ACP session withmcpServers: []. Integrated agents get no SproutGit tools at all — an agent that wants to create a worktree, check PR state, or fan out subtasks has to shell out to rawgit/ghand hope for the best. All the agent-facing capability we're building (#137 fan-out, #138 PR lifecycle, #135 base-aware worktree creation) would otherwise only be reachable by humans.Proposal
SPROUTGIT_MCP_URLor a socket path) so CLIs that support MCP config can attach.This is the piece that makes the orchestration epic agent-agnostic: any ACP-speaking agent — including ad-hoc ones from the roster issue — gets the same tools as the built-in presets, with zero per-agent integration work.