Bug: Squad didn't pick the right github repo for issues

I'm in copilot cli inside vs code, with a github repo open. Only one remote. Asked it to work on numbered issues and it decided I must be talking about bradygaster/squad issues.

I've only worked about 100 issues in this repo, mostly with squad. I've also seen it completely mis-diagnose my repo as Elixir, Go, TypeScript, and others (it's entirely PowerShell Universal).

Here's a transcript

● Selected custom agent: Squad

❯ let's fan out and finish #347 and #348.  I have popped the wip from the stash.  We'll include any squad/skill changes in this pr
● Squad v0.9.1 — I’m lining up the team for both issues and pulling the current squad context so we can split #347 and #348 cleanly, including any squad/skill
  updates that belong in the same PR.

● skill(github-issue) 

● Search (glob)
  │ "**/AGENTS.md"
  └ 1 file found

● Get user, repo root, branch, and worktrees (shell)
  │ git config user.name && git rev-parse --show-toplevel && git --no-pager branch --show-current && git worktree list --porcelain
  └ 9 lines...

● Read team.md
  │ .squad\team.md
  └ 30 lines read

● Read routing.md
  │ .squad\routing.md
  └ 47 lines read

● Read registry.json
  │ .squad\casting\registry.json
  └ 53 lines read

● Read AGENTS.md
  │ .github\agents\AGENTS.md
  └ 62 lines read

● Read now.md
  │ .squad\identity\now.md
  └ 10 lines read

✗ Get issue details (MCP: github-mcp-server) · owner: "bradygaster", repo: "UniversalAutomation", issue_number: 347, method: "get"
  └ MCP server 'github-mcp-server': McpError: MCP error 0: failed to get issue: GET https://api.github.com/repos/bradygaster/UniversalAutomation/issues/347: 404
    Not Found []

✗ Get issue details (MCP: github-mcp-server) · owner: "bradygaster", repo: "UniversalAutomation", issue_number: 348, method: "get"
  └ MCP server 'github-mcp-server': McpError: MCP error 0: failed to get issue: GET https://api.github.com/repos/bradygaster/UniversalAutomation/issues/348: 404
    Not Found []

🏗️ Squad Triage — Flight (Lead)

Issue: #905 — Bug: Squad didn't pick the right github repo for issues
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

Team roster:

Flight (Lead) → label: squad:flight
Procedures (Prompt Engineer) → label: squad:procedures
EECOM (Core Dev) → label: squad:eecom
FIDO (Quality Owner) → label: squad:fido
PAO (DevRel) → label: squad:pao
CAPCOM (SDK Expert) → label: squad:capcom
CONTROL (TypeScript Engineer) → label: squad:control
Surgeon (Release Manager) → label: squad:surgeon
Booster (CI/CD Engineer) → label: squad:booster
GNC (Node.js Runtime) → label: squad:gnc
Network (Distribution) → label: squad:network
RETRO (Security) → label: squad:retro
INCO (CLI UX & Visual Design) → label: squad:inco
GUIDO (VS Code Extension) → label: squad:guido
Telemetry (Aspire & Observability) → label: squad:telemetry
VOX (REPL & Interactive Shell) → label: squad:vox
DSKY (TUI Engineer) → label: squad:dsky
Sims (E2E Test Engineer) → label: squad:sims
Handbook (SDK Usability) → label: squad:handbook
Ralph (Work Monitor) → label: squad:ralph
@copilot (Coding Agent) → label: squad:copilot

To reassign, remove the current squad:* label and add the correct one.

@MikeShepard

Hi @MikeShepard, can you help us reproduce this? Specifically:

How many repos did you have cloned locally when this happened?
Was the repo you expected Squad to use the one in your current working directory?
What did \git remote get-url origin\ show in the directory where you ran Squad?
Did you have a .squad/team.md\ with an Issue Source section pointing to a specific repo?

Any additional context (OS, Squad version, CLI output) would help narrow this down. Thanks!

1. I think I have 4 different repos cloned. 3 are PowerShell Universal repos, and the 4th is a straight PowerShell repo. 2. Yes. 3. I'll have to check, but when I told squad to use the remote for the repo that was open, it got the right issue. 4. Yes. I've been using squad for a couple of weeks and have had dozens of sessions. I've tried several varieties of prompts to get it to get the right repo to start with, and finally had it write the remote into Agents.md. I don't think I've had any problems with it since. Before that, it was a frequent occurrence, often with somewhat comical results.

…

On Sun, Apr 12, 2026 at 3:44 AM Tamir Dresher ***@***.***> wrote: *tamirdresher* left a comment (bradygaster/squad#905) <https://github.com/bradygaster/squad/issues/905#issuecomment-4231138860> Hi @MikeShepard <https://github.com/MikeShepard>, can you help us reproduce this? Specifically: 1. How many repos did you have cloned locally when this happened? 2. Was the repo you expected Squad to use the one in your current working directory? 3. What did \git remote get-url origin\ show in the directory where you ran Squad? 4. Did you have a .squad/team.md\ with an Issue Source section pointing to a specific repo? Any additional context (OS, Squad version, CLI output) would help narrow this down. Thanks! — Reply to this email directly, view it on GitHub <https://github.com/bradygaster/squad/issues/905#issuecomment-4231138860>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKI2IUYGZBMG522G7AXTX34VNJPDAVCNFSM6AAAAACXP5CWLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZRGEZTQOBWGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- https://powershellstation.com

fix: Squash the Gremlins — 5 bug fixes (github#920, github#1062, gith…

Navigation Menu

Repository navigation

Bug: Squad didn't pick the right github repo for issues #905

🏗️ Squad Triage — Flight (Lead)

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Bug: Squad didn't pick the right github repo for issues #905

Description

Activity

github-actions commented on Apr 8, 2026

🏗️ Squad Triage — Flight (Lead)

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

tamirdresher commented on Apr 12, 2026

MikeShepard commented on Apr 13, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions