You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Old CLI versions have no in-CLI path to discover or install updates #148
Needs investigation / reproduction. No investigate or reproduce label exists on this repo — feel free to relabel.
What I hit
I had supermodel 0.5.1 installed on macOS (arm64) for ~3 days. There was no indication from the CLI that I was behind, and supermodel update did not exist in that version, so I had no in-CLI way to upgrade.
The only path I found to upgrade was re-running the curl install script:
$ curl -fsSL https://supermodeltools.com/install.sh | sh
Installing supermodel v0.6.10 (darwin/arm64)…
$ supermodel version
supermodel 0.6.10 (786aa72, 2026-04-16T17:45:09Z)
After upgrading, update works as expected:
$ supermodel update --check
supermodel 0.6.10 is up to date
Why this is a problem
v0.6.0 → v0.6.10 shipped a lot of fixes and features (including update and skill themselves) in ~3 days. A user on v0.5.x or earlier has zero CLI signal that any of it exists.
The "unknown command" error from update on old versions doesn't hint at the real cause (their binary is too old).
Anyone who installed via Homebrew or npm and forgot to re-run their package manager is silently stuck.
Suggestions to investigate
Startup version-check — once per day (or on a configurable interval), the CLI hits the GitHub releases API and prints a one-line banner if a newer version is available. npm and gh both do this; cheap to implement.
Friendlier unknown command message on old binaries — hard, since the old binary can't know what's been added later. But the install script could leave a ~/.supermodel/.installed-version file and a wrapper, or the GitHub release notes could mention "if you're on < 0.6.0 you need to re-install."
Auto-update on supermodel setup — the wizard already runs end-to-end; checking for a newer version at the start would catch most users.
Reproduce
# install an older version (replace 0.5.1 with whatever's available)
gh release download v0.5.1 --repo supermodeltools/cli --pattern '*darwin_arm64*'
tar -xzf supermodel_*_darwin_arm64.tar.gz
./supermodel update # ← unknown command
./supermodel version # ← no warning that 0.6.10 exists
Environment
macOS Darwin 25.2.0, arm64
Originally installed via curl -fsSL https://supermodeltools.com/install.sh | sh
#49 - Add first-run detection and install-time setup wizard [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
@jonathanpopham we don't need to worry about supporting old versions because we're in alpha. I support the update detection and friendly reminders to the user when there's a new version as a feature added in the next major patch. We cannot go back in time and update our older npm releases or update the already installed older versions on user's computers.
Activity
coderabbitai commentedon Apr 29, 2026
🔗 Related PRs
#49 - Add first-run detection and install-time setup wizard [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
greynewell commentedon Apr 30, 2026
@jonathanpopham we don't need to worry about supporting old versions because we're in alpha. I support the update detection and friendly reminders to the user when there's a new version as a feature added in the next major patch. We cannot go back in time and update our older npm releases or update the already installed older versions on user's computers.