## Context Part of #10: Copilot client parity across surfaces. ## Problem As we test Squad on VS Code, JetBrains, and GitHub.com, we need a single source of truth documenting what works where. ## Deliverable Create a compatibility matrix document showing: | Feature | CLI | VS Code | JetBrains | GitHub.com | |---------|-----|---------|-----------|-----------| | Sub-agent spawn | `task` | `runSubagent` | ? | ? | | Model selection | ✅ | ? | ? | ? | | Background exec | ✅ | ? | ? | ? | | .ai-team/ access | ✅ | ? | ? | ? | | File discovery | ✅ | ? | ? | ? | Include: - Row for each feature/capability - Column for each client surface - ✅ (works), ❌ (not available), ? (untested), ⚠️ (limited/degraded) - Notes on parameter differences, fallbacks, or workarounds - Link to detailed investigation issues (#11, #12, #13) ## Location Place in docs/features/client-parity.md or docs/scenarios/client-compatibility.md ## Success Criteria - [ ] Compatibility matrix created with all tested surfaces - [ ] CLI column is 100% verified - [ ] VS Code column populated from #11, #12, #13 results - [ ] Documentation includes fallback strategies - [ ] Added to main docs navigation ## Related - Parent: #10 (Copilot client parity) - Depends on: #11, #12, #13 (VS Code investigations)
Activity
bradygaster commentedon Feb 13, 2026
Compatibility matrix shipped at docs/scenarios/client-compatibility.md. Synthesized findings from spikes #32, #33, #34.
docs(ai-team): merge McManus decision on client parity matrix
feat: project board + v0.4.0 docs (#6)