Update AGI Cockpit
Check and apply AGI Cockpit updates on Windows, macOS, or Linux, then inspect update state and diagnostic logs if an update fails.
The update method depends on how AGI Cockpit is distributed. This guide identifies the method for your environment and verifies the result after updating.
AGI Cockpit and the external agent CLIs are updated separately. Under Settings → Updates, open Agent CLIs to compare installed and latest versions for Claude, Codex, Antigravity, Cursor, Qoder, Grok Build, and Muse Code. Check refreshes one agent's status. When Cockpit knows an update command, Update CLI opens a terminal to run it on the host; it does not update the Cockpit app. The read-only equivalent is cockpit setup agent status <agent>.
1. Check the update method
Open the update notice in the lower-left corner or select Updates from the app menu. From the CLI, inspect the current update capability and state with:
cockpit update status
| Environment | Update method |
|---|---|
| Packaged macOS build | Cockpit checks, downloads, and installs the update |
| Packaged Linux build | Cockpit checks for the update; you replace the AppImage or .deb manually |
| Windows Store build | Update through Microsoft Store |
| Development or unsupported build | Find the appropriate package on the distribution page |
2. Apply the update
On macOS, use the on-screen action to restart and install after the download finishes. From the CLI, wait for the download, confirm that running tasks can end, then install:
cockpit update check --wait-download
cockpit update install --confirm
A successful cockpit update install --confirm restarts AGI Cockpit and terminates every running task.
On a packaged macOS build with a downloaded update, select Install when idle to start installation after no task or Fleet Run is running. The CLI equivalents are:
cockpit update install-when-idle
cockpit update cancel-install-when-idle
The schedule exists only for the current app session and is cleared by an AGI Cockpit restart. If no task or Fleet Run is already running, installation can begin immediately after arming. A task awaiting input or an Ask, and a paused Fleet Run, do not block it. When installation begins, every task ends, including waiting tasks. Inspect the count and armed state under scheduledInstall in cockpit update status; cancel it on screen or with cancel-install-when-idle before installation starts. This schedule is available only on packaged macOS builds that support automatic installation.
On Linux, open the language-matched download page from Update manually or the update notice, then replace the AppImage or .deb with the package for the current CPU architecture. On Windows, update AGI Cockpit from the Microsoft Store library.
Update from a phone
With an active AGI Labo membership and an authenticated PWA connection, open the connection target in the header and select Host updates. You can check the host version, release notes, and download progress. Automatic installation is available for packaged macOS hosts after the download completes. Update now requires a separate confirmation because it restarts the host and terminates every running task.
After the download completes, Install when idle arms installation for the point when no task or Fleet Run is running. The PWA shows the current blocking count and lets you cancel the schedule before installation starts. The schedule is session-only; a host restart clears it. Tasks waiting for input or an Ask and paused Fleet Runs do not block installation, and every task ends once installation begins.
The PWA attempts to reconnect automatically after restart. Linux hosts require manual installation on the host, and Windows Store hosts update through Microsoft Store. See Remote access for the full procedure and connection requirements.
3. Verify the update
After restart, open Updates or run cockpit update status to inspect the current state and last install result. See Release history for the published changes.
If the update fails
Cockpit retries an update check once after a temporary network or server failure. If it still fails, select Try again or Update manually. Cockpit does not continue with automatic installation when it cannot validate the update data.
On macOS, if the app has not quit within five minutes after an install request, Cockpit records the stalled handoff and retries the install request once. Diagnostic events for update checks, downloads, verification, installation, and restart are stored in ~/.agi-tools/data/cockpit/logs/updater.jsonl.
Use cockpit update status to inspect the last error and install result. If the problem remains, follow the reporting guidance in Reference and support.