- Shipped
- August 25, 2026 at 3:11 PM UTC
- Author
- Kamo
- Commit
- 7104e1a
sage's VS Code is a multi-root workspace holding all 63 repositories, so taking the first workspace folder rooted a bug about the login site in aiservice — the list is alphabetical, not meaningful. Verified against the live agent: the session landed in **************** before this and -home-sage-Kamo-Projects after. The common parent is also the useful answer: a bug report rarely names the right repository, so the session needs to see across them. Required to sit under sage's home, so a workspace spanning unrelated trees falls back rather than starting a session at the root of the filesystem.