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

# Install the CLI

> Install the floo CLI on macOS, Linux, or Windows, pin a version, keep it updated, and install the tools floo works alongside.

```bash theme={null}
curl -fsSL https://getfloo.com/install.sh | bash
floo version
```

The script downloads the release for your platform, checks its SHA-256, and
installs `floo` to `/usr/local/bin`. If that directory is not writable, it
asks for `sudo`.

## Supported platforms

| OS | Architectures | Install |
| - | - | - |
| macOS | Apple Silicon (arm64), Intel (x86\_64) | Install script |
| Linux | x86\_64, arm64 | Install script |
| Windows | x86\_64 | Download `floo-x86_64-pc-windows-msvc.exe` from [GitHub Releases](https://github.com/getfloo/floo-cli/releases), rename it `floo.exe`, and add its folder to your `PATH` |

## Install options

Set these before `bash`:

| Variable | Effect | Example |
| - | - | - |
| `FLOO_INSTALL_DIR` | Install somewhere other than `/usr/local/bin`, for example without `sudo`. The directory must be on your `PATH` | `FLOO_INSTALL_DIR="$HOME/.local/bin"` |
| `FLOO_INSTALL_VERSION` | Pin a release tag instead of the latest | `FLOO_INSTALL_VERSION=v2026.10.27` |

```bash theme={null}
curl -fsSL https://getfloo.com/install.sh | FLOO_INSTALL_DIR="$HOME/.local/bin" bash
```

Pin a version in CI so a new release cannot change a pipeline mid-run.

## Sign in

```bash theme={null}
floo auth login
```

The CLI opens your browser to finish sign-in and stores a key in
`~/.floo/config.json`. For CI and other machines without a browser, use a
floo API key; see [floo API keys](https://getfloo.com/docs/guides/team-access.md#floo-api-keys).

## Keep it updated

`floo version` checks for a newer release and installs it. Releases are
date-versioned, such as `2026.10.27`. Set `FLOO_NO_UPDATE_CHECK=1` to skip the
check. See [update](https://getfloo.com/docs/cli/update.md).

## Tools floo works alongside

* **git**, to commit and push. floo deploys from GitHub, never from your
  working directory.
* **The GitHub CLI (`gh`)**, optional, to publish prod releases with
  `gh release create`. The GitHub web UI works too; see
  [Environments](https://getfloo.com/docs/guides/environments.md#the-flow).
* **Docker**, optional, only to test your image locally. floo builds the image
  for you.

## Next steps

> **[Quickstart](https://getfloo.com/docs/introduction.md)**
>
> Connect a repo and get a live dev URL.

> **[CLI overview](https://getfloo.com/docs/cli/overview.md)**
>
> Every command group and the JSON output contract.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.