Repository navigation
Grasshopper 2.11.0
Grasshopper 2.11.0
Updates now take care of themselves across machines.
- Releases publish when a VERSION change merges; no tag push needed.
- Clients follow the server: the bridge downloads the client matching the
server's version, checks it against SHA256SUMS and switches to it. Opt out
with an updates-off file beside client.json. - grasshopper-server upgrade on macOS backs up the database, switches a
current link to the new archive, restarts the launchd job and restores the
old version if health fails. upgrade --rollback goes back; upgrade
--schedule runs it nightly.
Plugins need one manual update to 2.11.0; after that, clients update with the
server.
Which file?
| Purpose | Download or install |
|---|---|
| Server on Apple silicon macOS | grasshopper-server-darwin-arm64-2.11.0.zip |
| Server on Linux x86-64 | grasshopper-server-linux-amd64-2.11.0.zip |
| Server on Windows x86-64 | grasshopper-server-windows-amd64-2.11.0.zip |
| Client CLI or Claude archive on Apple silicon macOS | grasshopper-client-darwin-arm64-2.11.0.zip |
| Client CLI or Claude archive on Linux x86-64 | grasshopper-client-linux-amd64-2.11.0.zip |
| Client CLI or Claude archive on Windows x86-64 | grasshopper-client-windows-amd64-2.11.0.zip |
| Agent plugins | Follow setup; no archive needed |
| Marketplace maintenance | grasshopper-marketplace-2.11.0.zip |
Check downloads against SHA256SUMS. Executables are unsigned; see
unsigned archives.
Before updating a server, follow back up and update
and keep the previous archive for rollback.