Repository navigation
Manual verify: Client compatibility (#47) #420
Description
Feature: VS Code extension host compatibility — squad runtime in extension context.
Why manual verification needed:
- Requires VS Code Extension Development Host
- Involves LSP integration and extension API surface
- Environment-specific: Node.js runtime within VS Code's sandboxed environment
Test approach:
- Load Squad in VS Code Extension Development Host
- Start an agent session from the extension
- Verify tool execution (file reads, shell commands, git operations)
- Test streaming responses in the extension UI
- Test multi-turn conversations
- Verify resource cleanup on window close
Success criteria:
- ✅ Squad runtime initializes without errors in extension context
- ✅ All tools work correctly (file I/O, shell, git)
- ✅ Streaming responses render properly in VS Code UI
- ✅ No path resolution failures (workspace vs extension paths)
- ✅ Clean shutdown without orphaned processes
Related: Issue #47
Activity
github-actions commentedon Mar 15, 2026
📋 Assigned to FIDO (Quality Owner)
Issue: #420 — Manual verify: Client compatibility (#47)
FIDO will pick this up in the next Copilot session.
test: SDK feature parity tests for #340
test: SDK feature parity tests for #340 (#422)
Fix github#422: Add context to thinking spinner (github#436)
Fix github#420/github#425: Add SDK connection feedback (github#437)
bradygaster commentedon Mar 24, 2026
Closing for now — will reopen once SDK-first (#341, #347) is complete. Client compatibility verification depends on SDK parity being finished first.