Repository navigation
VS Code: Test and document runSubagent as Squad spawn mechanism #32
Description
Context
Part of #10: Copilot client parity across surfaces. VS Code is the priority.
Problem
VS Code Copilot uses runSubagent instead of the CLI's task tool. We need to validate that Squad can detect VS Code and use runSubagent correctly.
Key Questions to Investigate
- Can squad.agent.md detect it's running in VS Code and switch from
tasktorunSubagent? - What parameters does
runSubagentsupport? (model, mode, description, model override) - Does background/async execution work? Can results be collected?
- What's the fallback behavior if
runSubagentis not available?
Success Criteria
- Document VS Code agent spawn behavior (compatibility layer or conditional logic)
- Write test/demo showing
runSubagentcall succeeding in VS Code - Document parameter parity (or gaps) with CLI
tasktool - Define fallback strategy for missing parameters
- Update squad.agent.md with VS Code detection logic
Related
- Parent: Copilot client parity: Squad works fully only on GitHub Copilot CLI #10 (Copilot client parity)
- Blocks: Feature: Enable MCP use #11, Add @copilot coding agent as a Squad member type #12, Add @copilot coding agent as a Squad member type #13 (other VS Code investigations)
Activity
bradygaster commentedon Feb 13, 2026
Spike Complete ✅
Strausz and Kujan completed parallel research on
runSubagentvs CLItasktool parity.Key Findings
runSubagentis viable for Squad's VS Code spawn mechanismsquad.agent.mdare sufficienttasktool (CLI) vsrunSubagent/agenttool (VS Code).agent.mdfiles per roleGaps (both manageable)
mode: "background"— mitigated by parallel sync subagentsmodelparam — mitigated by custom.agent.mdfiles (v0.4.x)Deliverables
team-docs/proposals/032a-runsubagent-api-research.md— Strausz's VS Code API researchteam-docs/proposals/032b-cli-spawn-parity-analysis.md— Kujan's CLI parity analysis.ai-team/skills/cross-platform-agent-spawning/SKILL.md— Reusable skill for multi-surface spawningRecommended Path
squad.agent.md. Accept session model for all VS Code spawns..agent.mdfiles duringsquad initfor per-agent model selection.agentsfrontmatter restrictions anddisable-model-invocation.Ready to move to #33 (file discovery) and #34 (model selection parity).
[-]VS Code: Test and document \ unSubagent\ as Squad spawn mechanism[/-][+]VS Code: Test and document runSubagent as Squad spawn mechanism[/+]bradygaster commentedon Feb 13, 2026
Spike complete. Proposals 032a (runSubagent API research) and 032b (CLI parity analysis) shipped to team-docs/proposals/. Findings fed into #33, #34, and #35.
docs(ai-team): add Strausz as VS Code Extension Expert
docs(ai-team): log VS Code parity spike and merge decisions
feat: project board + v0.4.0 docs (#6)
feat: extract watchdog scripts from corrupted branches (filter, extra…