Updates
How Agent Grid auto-updates and how to force a clean reinstall.
Agent Grid ships an auto-updater so installed copies stay current with the latest release. This page covers how the updater works and how to force a reinstall when the updater can't make progress.
How auto-update works
Agent Grid uses electron-updater configured against a generic provider. The updater checks the release feed at:
https://gsquusa98lgqvrg5.public.blob.vercel-storage.com/releases/…on channel latest. On startup (and on a schedule while the app is running) it fetches the channel manifest, compares it against the running version, and downloads the new build in the background if one is available. The app prompts to restart once the download is staged.
The same release storage backs the marketing site's download page. /api/download/{mac|win|linux-appimage|linux-deb} on agentgrid.sh proxies straight to it.
Update channel and platforms
| Platform | Target | Channel | Architecture |
|---|---|---|---|
| macOS | .dmg, .zip | latest | arm64 (Apple Silicon) and x64 (Intel) |
| Windows | NSIS .exe installer | latest | x64 |
| Linux | .AppImage and .deb | latest | electron-builder default |
macOS ships both arm64 and x64 dmgs. electron-updater picks the build that matches the running Mac from the same latest-mac.yml manifest — Apple Silicon and Intel each auto-update to their matching arch.
When auto-update can't progress
If the app reports an update failure, or you want to drop back to a clean state, force a reinstall:
- Quit Agent Grid fully (check the tray / dock — the single-instance lock means a hidden copy will block a fresh launch).
- Download the latest installer from agentgrid.sh/download.
- Run the installer over the top of the existing install. On macOS, drag the new
.appinto/Applicationsand replace. - Launch Agent Grid. Your
userDatadirectory carries over, so spaces, recent projects, and paired mobile devices stay intact.
If you want to also reset state, delete the userData directory between steps 1 and 4 — see Logs and diagnostics.
Code signing and notarization
The macOS build runs with the hardened runtime and is notarized by Apple. If macOS refuses to open the app the first time, right-click the .app and choose Open to bypass the Gatekeeper warning once.
The Windows NSIS installer is unsigned for now; expect a SmartScreen warning on first run.