> ## Documentation Index
> Fetch the complete documentation index at: https://www.floe.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Update the Floe CLI

> Keep the floe CLI up to date on macOS, Windows, and Linux using the built-in self-update command or by reinstalling the latest release binary.

## Package manager installs

If you installed floe via a package manager, use the standard upgrade command for that tool.

| Install method   | Upgrade command                 |
| ---------------- | ------------------------------- |
| Homebrew (macOS) | `brew upgrade floe`             |
| Winget (Windows) | `winget upgrade jannskiee.floe` |
| Scoop (Windows)  | `scoop update floe`             |

## Script and manual installs

Run the built-in update command:

```bash theme={null}
floe update
```

This checks the latest release on GitHub, downloads the correct archive for your OS and
architecture, verifies the SHA-256 checksum, and replaces the running binary in place.

To check for an update without installing:

```bash theme={null}
floe update --check
```

To suppress the update hint shown by `floe version`, set `FLOE_NO_UPDATE_CHECK=1`.

You can also re-run the original install script at any time to upgrade:

```bash theme={null}
# macOS / Linux
curl -fsSL https://floe.one/install.sh | sh

# Windows
irm https://floe.one/install.ps1 | iex
```

## Version compatibility

You do not need to match versions with the person on the other end. Floe peers on different releases interoperate, so a small version difference is never a problem. In the rare case a release changes the transfer protocol in a breaking way, Floe detects it before any data moves and tells whichever side is older to update. See [Protocol versioning](/docs/reference/architecture#protocol-versioning) for the details.