Repository navigation
question: squad upgrade CLI not working #597
Description
Context
- i have squad globally installed via
npm - when i run
squad --versionin myD:root i see: 0.8.25 - i run
squad upgradeand i see the following:
✗ No squad found — run init first.- if i navigate into a repo with an active squad and run the following:
squad --version - i see 0.8.25
- if i run
squad upgradei see:
Already up to date (v0.8.25)
✓ upgraded squad workflows (11 files)
✓ upgraded squad.agent.mdAssumption
- i don't see anything in my
package.jsonornode_modulesaboutsquad - so
squad upgradeshould work on my global installation (cwd agnostic) esp. ifsquad --versionreturns a version here. - seeing a version globally but requiring a
squad initbefore being able to upgrade versions is a little confusing - seeing a version locally (inside repo with squad init already) but then running
squad upgradeand not finding the latest version to install seems like a bug.
AC
- I just want to update my global installation of squad to the latest version 🫠
- Maybe there should be a command to pull down the latest version? if not maybe we could align the installation documentation to specificy the
npm install -g @bradygaster/squad-cli@latestrequirement (see below)
- Maybe there should be a command to pull down the latest version? if not maybe we could align the installation documentation to specificy the
References (Docs)
- the following locations are all i could find on upgrading and they are all outdated:
- https://bradygaster.github.io/squad/docs/scenarios/upgrading/
- missing information about explicit
npmre-install
- missing information about explicit
- https://github.com/bradygaster/squad?tab=readme-ov-file#upgrading
- this is the correct workflow (re-install global via
npmwith@latestargument, thensquad upgrade
- this is the correct workflow (re-install global via
- https://www.npmjs.com/package/@bradygaster/squad-cli?activeTab=readme#installation
- npm isn't specifically wrong, but doesn't have great coverage on how to update
cli.jsin source code deprecation warnings: (should include@latest?)
- https://bradygaster.github.io/squad/docs/scenarios/upgrading/
console.error(' Switch to: npm install -g @bradygaster/squad-cli');
console.error(' Or use: npx @bradygaster/squad-cli');
Activity
colinwilliams91 commentedon Mar 24, 2026
Actually, the only valuable piece of information in this ticket are the docs links above in my issue description (## References (docs))
Once I realized I needed to re-install the global package from npm and was updated to 9.x.x it appears that the source code handles explicitly instructing the user to update via npm with a combination of this function:
notifyIfUpdateAvailableinself-update.tsL:94 and control flow inside the CLI in a banner.So, I don't really think anything needs to be done here. I suppose docs could be updated so I'll leave the ticket open for a little bit.
fix: REPL UX fixes — 10 issues resolved with 52 new tests (github#608)
bradygaster commentedon Mar 26, 2026
Thanks so much for the thorough bug report, @colinwilliams91! Your detective work on the docs references was really helpful.
We've confirmed your findings:
otifyIfUpdateAvailable\ banner in \self-update.ts\ already handles upgrade hints correctly (with @latest)
Thanks again for catching this and helping us improve the experience! 🙌
fix: add @latest to npm install commands in cli.js and package README (…
feat(cli): add squad config model command for model pinning (#618) (#628