Repository navigation
Does the npx github:bradygaster/squad --version show the installed version or latest version? #137
Description
I am on v0.4.1 and I was investigating doing an update. I ran the following:
npx github:bradygaster/squad --version
0.5.2 was returned not 0.4.1.
I verified that .github/agents/squad.agent.md had 0.4.1 version as shown below:
`
name: Squad
description: "Your AI team. Describe what you're building, get a team of specialists that live in your repo."
You are Squad (Coordinator) — the orchestrator for this project's AI team.
Coordinator Identity
- Name: Squad (Coordinator)
- Version: 0.4.1 (see HTML comment above — this value is stamped during
`
I ran the npx upgrade and it did in fact upgrade my repo from 0.4.1 to 0.5.2. The documentation states that the --version flag returns the installed version but I did not experience that.
Reacted by Sturla Thorvaldsson
Activity
jeremythake commentedon Feb 26, 2026
hitting the same issue using
--versionfix: Windows EPERM fallback (#135) + --version shows installed (#137)
fix: Windows EPERM fallback (#135) + --version shows installed (#137)
bradygaster commentedon Feb 27, 2026
Fixed in PR #149 (merged to dev). --version now shows both versions:
Package: 0.5.3 (the npx-fetched version)
Installed: X.X.X (read from squad.agent.md in your repo)
This makes it clear what version your repo has vs. what's latest on GitHub.
bradygaster commentedon Feb 27, 2026
Fixed in PR #149 (merged to dev).
--versionnow shows both lines:Package: X.X.X(the npx-fetched version) andInstalled: X.X.X(read fromsquad.agent.mdin your repo). If Squad isn't installed yet, it showsInstalled: not installed. Will ship in the next release.docs(ai-team): Log Fenster CLI fixes session
chore: merge fix for #135 (Windows EPERM) and #137 (--version) into dev
chore: merge dev for v0.5.3 release
feat(.squad): wire workflow guide into squad.agent hiring process (gi…
Merge squad/137-wire-pr-lifecycle: workflow wiring guide + issue-life…