Title: bug: VSCode Autopilot breaks Squad agent execution · Issue #613 · github/squad · GitHub
Open Graph Title: bug: VSCode Autopilot breaks Squad agent execution · Issue #613 · github/squad
X Title: bug: VSCode Autopilot breaks Squad agent execution · Issue #613 · github/squad
Description: Squad routing fails to be applied during Autopilot-driven work. Although specialist roles and routing rules are defined, Autopilot continues execution as the active agent instead of dispatching work to the assigned Squad specialists. Thi...
Open Graph Description: Squad routing fails to be applied during Autopilot-driven work. Although specialist roles and routing rules are defined, Autopilot continues execution as the active agent instead of dispatching wor...
X Description: Squad routing fails to be applied during Autopilot-driven work. Although specialist roles and routing rules are defined, Autopilot continues execution as the active agent instead of dispatching wor...
Opengraph URL: https://github.com/github/squad/issues/613
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bug: VSCode Autopilot breaks Squad agent execution","articleBody":"Squad routing fails to be applied during Autopilot-driven work. Although specialist roles and routing rules are defined, Autopilot continues execution as the active agent instead of dispatching work to the assigned Squad specialists. This results in specialist-scoped work being performed outside the intended routing model.\n\n## What Is Failing\n\nSquad routing rules exist and are correctly defined.\nHowever, they are not enforced by Autopilot or the editor runtime.\nIf the coordinator does not explicitly invoke the Squad flow, routing is silently bypassed.\nAs a result, work that clearly matches specialist ownership continues inline with the coordinator.\n\n## Expected Behavior\n\nWhen Squad mode is active, requests that match routing rules should be dispatched to the assigned specialists.\nIf routing is advisory-only, this must be clearly disclosed.\nIt should be explicit whether work is being done inside or outside Squad routing.\n\n## Actual Behavior\n\nAutopilot continues as the active coding agent even when routing rules apply.\nSpecialist configuration gives a false sense of enforcement.\nSpecialist reasoning may inform decisions, but execution remains with the coordinator.\nThis creates a mismatch between perceived and actual ownership.\n\n## Impact\n\nSpecialist ownership boundaries are broken.\nCoordinator and specialist responsibilities are mixed.\nTraceability, review expectations, and accountability are weakened—especially during critical-path work.\n\n## Root Cause (Confirmed)\n\nSquad configuration (team.md, routing.md) is guidance only.\nIt is not an enforcement layer.\nRouting only happens if the coordinator explicitly hands off the task. When that does not occur, the system fails silently.\n\n## Why This Matters\n\nThe current behavior breaks the Squad mental model. Users reasonably expect routing rules to either:\n\nbe enforced, or\nclearly fail loud.\n\nRight now, routing fails quietly, which is the worst possible mode during high-risk or release-critical work.\n\n``` \nUser: \nWhy is it not using the squad agent here? There are rules!\n\nAgent: \n\nSquad v0.8.25-build.4\n\nBecause I violated the repo’s workflow. I continued as the active coding agent in this VS Code chat instead of dispatching through the Squad coordinator and the CEHub specialists.\n\nThe rules exist in the repo, but they are not hard-enforced by VS Code Autopilot on every turn. They only take effect if the active session actually routes through the Squad coordinator path and launches the relevant agents. In this session, that handoff did not happen, and I incorrectly kept working inline. That is the exact failure mode you called out.\n\nConcretely:\n\nThe roster and routing in [.squad/team.md](vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/cfbea10c5f/resources/app/out/vs/code/electron-browser/workbench/workbench.html) and [.squad/routing.md](vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/cfbea10c5f/resources/app/out/vs/code/electron-browser/workbench/workbench.html) are guidance unless I actually invoke the Squad flow.\nI should have routed CEHub extension work to Reginald Barclay and MCP/backend work to Tasha Yar instead of editing directly.\nThat was my mistake, not a missing repo rule.\nIf you want, I’ll correct course from here in one of two ways:\n\nStop all inline work and re-run this through Squad specialists only.\nFinish the cookie-session test implementation myself, but explicitly note that it is outside Squad routing.\n```","author":{"url":"https://github.com/andikrueger","@type":"Person","name":"andikrueger"},"datePublished":"2026-03-25T19:25:32Z","url":"https://github.com/github/squad/issues/613"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f3dc07d8-fe29-fc1f-db0e-674c22dd8b27 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A984:395430:1AA98D5:232972C:6B014940 |
| html-safe-nonce | 36090ccf69f93b996b9fe20bb14dc01c92a6a547f85b022d05b870a910bbf762 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBOTg0OjM5NTQzMDoxQUE5OEQ1OjIzMjk3MkM6NkIwMTQ5NDAiLCJ2aXNpdG9yX2lkIjoiMjcyNzE0Mjk4ODc5ODA1MjY3MiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | c75ce47b7c23e7e161341ef5aea65232e3eb9a13aeffb4b98b9d1cfc1de856a8 |
| hovercard-subject-tag | issue:4137943195 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/github/squad/613/issue_layout |
| twitter:image | https://opengraph.githubassets.com/27515c20c38ae16d8081a3f5071cb1ec26b56fa9bcd621bbdb616276bc16c62b/github/squad/issues/613 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/27515c20c38ae16d8081a3f5071cb1ec26b56fa9bcd621bbdb616276bc16c62b/github/squad/issues/613 |
| og:image:alt | Squad routing fails to be applied during Autopilot-driven work. Although specialist roles and routing rules are defined, Autopilot continues execution as the active agent instead of dispatching wor... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | andikrueger |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/github/squad git https://github.com/github/squad.git |
| octolytics-dimension-user_id | 9919 |
| octolytics-dimension-user_login | github |
| octolytics-dimension-repository_id | 1151205052 |
| octolytics-dimension-repository_nwo | github/squad |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1151205052 |
| octolytics-dimension-repository_network_root_nwo | github/squad |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | canary-1 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width