AgentGridAgentGrid Docs
Troubleshooting

Updates

How AgentGrid auto-updates and how to force a clean reinstall.

AgentGrid ships an auto-updater so installed copies stay current with the latest release. You can let it run automatically or manage updates from Settings -> Updates.

How auto-update works

AgentGrid uses electron-updater against the public GitHub Releases repository:

https://github.com/agent-grid/agent-grid-releases/releases

On startup (and on a schedule while the app is running) it resolves the latest stable release metadata, compares it against the running version, and downloads the immutable versioned build in the background if one is available. The Update ready banner appears once the download is staged.

In Settings -> Updates you can:

  • See the current version, update status, staged version, and last check time.
  • Run Check for updates manually.
  • Turn automatic background updates on or off.
  • Install a staged update immediately.

If panes are still active, Install and restart offers Restart when finished. AgentGrid waits for the active sessions to become idle before restarting; you can cancel the pending restart or choose Install now later.

Previously installed builds still read the legacy Vercel Blob updater feed. During the migration window, each release also publishes versioned binaries and updater metadata there so those installations can move onto a GitHub-enabled version.

The public release repository backs the marketing site's download page. /api/download/{mac|win|linux-appimage|linux-deb} on agentgrid.sh prefers verified GitHub release metadata and redirects to its immutable asset URL. Until the first complete GitHub release is available, the site falls back to the existing Blob downloads.

Update channel and platforms

PlatformTargetChannelArchitecture
macOS.dmg, .zipLatest stable releasearm64 (Apple Silicon) and x64 (Intel)
WindowsNSIS .exe installerLatest stable releasex64
Linux.AppImage and .debLatest stable releaseelectron-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:

  1. Quit AgentGrid fully (check the tray / dock — the single-instance lock means a hidden copy will block a fresh launch).
  2. Download the latest installer from agentgrid.sh/download.
  3. Run the installer over the top of the existing install. On macOS, drag the new .app into /Applications and replace.
  4. Launch AgentGrid. Your userData directory 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.

Windows releases are code-signed. A valid current installer should identify AgentGrid as the publisher rather than showing the older unsigned-build warning.

On this page