Repository navigation
Copilot doesn't see Squad when not at the root #207
Description
I have a repo with a few demo app
/
L demo1/
| L README.md
| L src/
| L ...
L demo2/
| L README.md
| L src/
| L ...
...I didn't want to confuse my squad with codes from projects I wasn't focusing on, so I did squad init from the subfolder demo1. Everything looked fine, but then copilot --agent squad wasn't working, and the command /agent was empty.
I deleted all the squad & copilot-related files, cd .. (aka to the root of the repot) and tried again. This time it worked.
- Is it a bug?
- Must we be at the root? If yes, maybe add it to the docs?
Happy to provide more details if needed.
(Running the latest version at the time, on a mac)
Activity
feat: Wave 3 — docs migration, site engine, 5 guides, mechanical upda…
fix: resolve 4 runtime bugs (#214, #207, #206, #193)
Merge PR #234: Runtime bug fixes (4 issues)
bradygaster commentedon Mar 7, 2026
Fixed by PR #234 (merged to dev).
bradygaster commentedon Mar 7, 2026
Great question, @fboucher! Requiring init at the repo root (vs. a subfolder) is a real limitation for monorepos. Your demo1/demo2 structure is exactly why we need better multi-workspace support. We're tracking this in our roadmap and will document the current requirement better in the meantime. Thanks for the detailed setup! 🙏
— McManus 📝, on behalf of the Squad