Troubleshooting
Common issues and fixes for Squad installation and usage.
npx github:bradygaster/squad appears to hang
Problem: Running the install command shows a frozen npm spinner. Nothing happens.
Cause: npm resolves github: package specifiers via git+ssh://git@github.com/.... If no SSH agent is running (or your key isn’t loaded), git prompts for your passphrase on the TTY — but npm’s progress spinner overwrites the prompt, making it invisible. This is an npm TTY handling issue, not a Squad bug.
Fix (choose one):
-
Start your SSH agent first (recommended):
eval "$(ssh-agent -s)" ssh-addThen re-run
npx github:bradygaster/squad. -
Disable npm’s progress spinner to reveal the prompt:
npx --progress=false github:bradygaster/squad -
Use HTTPS instead of SSH by configuring git:
git config --global url."https://github.com/".insteadOf git@github.com:
Reference: #30
gh CLI not authenticated
Problem: GitHub Issues, PRs, Ralph, or Project Boards commands fail with authentication errors.
Cause: The gh CLI isn’t logged in, or is missing required scopes.
Fix:
-
Log in:
gh auth login -
If using Project Boards, add the
projectscope:gh auth refresh -s project -
Verify:
gh auth status
Node.js version too old
Problem: npx github:bradygaster/squad fails with an engine compatibility error, or Squad behaves unexpectedly.
Cause: Squad requires Node.js 22.0.0 or later (enforced via engines in package.json).
Fix:
node --version
If below v22, upgrade Node.js:
- nvm (macOS/Linux):
nvm install 22 && nvm use 22 - nvm-windows:
nvm install 22 && nvm use 22 - Direct download: nodejs.org
Squad agent not appearing in Copilot
Problem: After install, squad doesn’t show up in the /agents list in GitHub Copilot.
Cause: The .github/agents/squad.agent.md file may not have been created, or Copilot hasn’t refreshed its agent list.
Fix:
-
Verify the file exists:
ls .github/agents/squad.agent.mdIf missing, re-run
npx github:bradygaster/squad. -
Restart your Copilot session — close and reopen the terminal or editor.
Upgrade doesn’t change anything
Problem: Running npx github:bradygaster/squad upgrade completes but nothing changes.
Cause: You may already be on the latest version, or npm cached an old version.
Fix:
-
Check current version in
.github/agents/squad.agent.md(frontmatterversion:field). -
Clear npm cache and retry:
npx --yes github:bradygaster/squad upgrade
Windows-specific issues
Problem: Path errors or file operations fail on Windows.
Cause: Some shell commands assume Unix-style paths.
Fix: Squad’s core uses path.join() for all file operations and is Windows-safe. If you see path issues:
- Use PowerShell or Git Bash (not cmd.exe)
- Ensure git is in your PATH
- Ensure
ghCLI is in your PATH