VS Code: Test agent file discovery and .ai-team/ access #33

Activity

1. bradygaster

   added

   go:yesReady to implementReady to implement

   release:v0.4.0Targeted for v0.4.0Targeted for v0.4.0

   type:spikeResearch/investigation — produces a plan, not codeResearch/investigation — produces a plan, not code

   on Feb 13, 2026
2. bradygaster commented on Feb 13, 2026

   

   bradygaster

   on Feb 13, 2026

   CollaboratorAuthor

   More actions

   033a: VS Code File Discovery and .ai-team/ Access — Spike Complete

   Author: Strausz (VS Code Extension Expert)
   Proposal: team-docs/proposals/033a-vscode-file-discovery.md

   Key Findings

   1. Agent discovery works out of the box. VS Code auto-discovers squad.agent.md from .github/agents/ on workspace load. No changes needed.

   2. Sub-agents inherit file tools by default. Unlike CLI (where sub-agents get a fixed toolset per agent_type), VS Code sub-agents inherit ALL parent tools including readFile, editFiles, createFile, fileSearch, etc. This is a net positive for Squad — every spawned agent can read/write .ai-team/ files without special configuration.

   3. Path resolution works as-is. The worktree resolution algorithm (git rev-parse --show-toplevel) works in VS Code via runInTerminal. Workspace root and git toplevel typically align. No changes needed.

   4. Read/write access confirmed. Agents can read all .ai-team/ files via readFile and write to decisions inbox, history, skills via editFiles/createFile. First-session writes require user approval (VS Code security feature), but this is one-time per workspace.

   5. Permission constraints are minor. Workspace Trust must be enabled. Access is workspace-scoped (not filesystem-wide). sql tool is CLI-only — not available in VS Code.

   6. Multi-root workspaces are problematic. Known VS Code bugs with path resolution in multi-root setups. Recommend documenting single-root as the supported configuration.

   Tool Name Mapping (CLI → VS Code)

   Operation	CLI	VS Code
   Read file	view	readFile
   Edit file	edit	editFiles
   Create file	create	createFile
   Search by name	glob	fileSearch
   Search contents	grep	codebase
   Shell command	powershell	runInTerminal

   Overall Assessment

   Squad's file discovery and .ai-team/ access work in VS Code with zero code changes. The instruction-level abstraction in squad.agent.md (describing operations, not tool names) naturally works across both surfaces. A small VS Code compatibility note is recommended but not blocking.

   Success Criteria Status

   • Document VS Code file discovery behavior
   • Test .ai-team/ read access from an agent in VS Code
   • Test .ai-team/ write access (decision logging, skill updates)
   • Document permission constraints and workarounds
   • Update squad.agent.md recommendations for VS Code (proposal includes specific language)
3. bradygaster commented on Feb 13, 2026

   

   bradygaster

   on Feb 13, 2026

   CollaboratorAuthor

   More actions

   Spike complete. Proposal 033a (VS Code file discovery) shipped. Key finding: zero code changes needed — instruction-level abstraction maps naturally to VS Code tools.
4. bradygaster

   closed this as completedon Feb 13, 2026
5. bradygaster

   added 2 commits that reference this issue on Feb 13, 2026

   docs(ai-team): merge 3 decisions from inbox and propagate updates

   ...

   29f664d

   feat: project board + v0.4.0 docs (#6)

   ...

   b915015
6. joniba

   added a commit that references this issue on Mar 26, 2026

   feat: add agent dashboard with squad-monitor integration

   ...

   This issue will close once commit b436125 is merged into the 'dev' branch.

   b436125
7. bradygaster

   added a commit that references this issue on Mar 27, 2026

   fix(scribe): add HARD GATE archival with two-tier thresholds to Scrib…

   ...

   This issue will close once commit 3cc22b4 is merged into the 'dev' branch.

   3cc22b4