# Updating Foxora

Foxora Desktop and CLI 5.0.3 use signed release artifacts. The web app updates automatically when a new production deployment is loaded.

![Updating Foxora in Foxora v5.0.3](/docs/images/v5.0.3/settings/about.webp)

## Desktop automatic updates

Foxora Desktop checks the signed update manifest for a newer compatible version. When an update is available, the sidebar shows **Update available**.

1. Save or finish any active work.
2. Select the update notice, or open **Settings → About → Check for updates**.
3. Review the target version and release notes.
4. Download and install the update.
5. Select **Restart to update** when the package is ready.
6. Return to **Settings → About** and confirm the new version.

You can also run **Check for Updates…** from the application menu or Command Center. Foxora verifies the updater signature before installation; do not replace the signed package with an installer from an unofficial mirror.

## Manual desktop update

If the in-app check cannot reach the manifest:

1. Confirm the [Foxora status page](https://foxora.ai/status) and your internet connection.
2. Download the current package from the [official download page](https://foxora.ai/download).
3. Quit Foxora after active tasks have finished.
4. Install the new package over the existing application.
5. Reopen Foxora and confirm the version under **Settings → About**.

Normal upgrades preserve tasks, settings, authentication, Memory Den data, and project references. Export important local data before troubleshooting with a reset or removal.

## Update the CLI

Run:

```bash
foxora update
foxora --version
foxora doctor
```

`foxora update` refreshes the CLI and its managed runtime. The CLI and Desktop can have separate release histories, so verify each surface independently.

## Update the web app

The web runtime is deployed centrally. Refresh `https://app.foxora.ai` to load the current production assets. If an old tab remains open across a deployment, finish or save active work, then reload it.

## Verify the update

After any update:

1. Confirm the displayed version.
2. Open an existing task and create a new task.
3. Run one small tool or workspace task.
4. If you use plugins, channels, browser control, or scheduled work, test one harmless representative action.
5. Keep the exact version, time, and error if a regression appears.

Do not clear local data merely because an update check fails. Diagnose the updater, network, runtime, and account layers separately.