0. Prerequisites & install

This page gets you to a working ffleet on your machine. Do it once; then head to the basic flow.

Forge Fleet runs on macOS and Linux. Windows isn't supported (WSL2 may work but is untested).

Host prerequisites

Docker. Forge Fleet runs every coding-agent environment inside a Docker container, so a working Docker daemon on the host is required. Install Docker Engine (Linux) or Docker Desktop (macOS/Windows) and confirm it works:

$ docker run --rm hello-world

If that prints Docker's hello message, you're set. ffleet talks to the same daemon.

Note: Forge Fleet does not use Docker-in-Docker. If you need Docker inside an environment (e.g. the agent runs docker build), that's Docker outside Docker — see advanced/docker-dood.md.

Using a non-default Docker daemon. ffleet runs the standard docker CLI and inherits its configuration, so it talks to whatever daemon your CLI does — a remote host via DOCKER_HOST, a selected docker context, or a rootless / Colima / OrbStack socket. If docker ps works in your shell, ffleet works the same way; there's no separate ffleet setting. (One exception: Docker-outside-Docker assumes a local socket at /var/run/docker.sock and won't work against a remote or non-default-path daemon.)

Coding-assistant accounts & auth

Forge Fleet launches a coding assistant inside the container; it does not provide one. You need an account and working local credentials for at least one of:

Claude Code — Anthropic's CLI. Authenticate it on the host (e.g. log in, or run claude setup-token, or set ANTHROPIC_API_KEY). Its config/credentials live in ~/.claude.
OpenAI Codex — its config/credentials live in ~/.codex.

Forge Fleet mounts those host directories into the container so the agent is already authenticated inside — you don't re-login per environment. Exactly how credentials are selected and injected is covered in advanced/container-config.md and the [claude] / [codex] sections of the config reference.

Install

The recommended way to install ffleet is via Homebrew (works on macOS and Linux):

$ brew tap grzegorz-aniol/tap
$ brew install ffleet

Then verify:

$ ffleet version
ffleet 1.x.y (commit …, built …, linux/amd64, go1.xx)

Fallback: manual binary download

No Homebrew? ffleet is also distributed as a prebuilt binary from the public distribution repo:

https://github.com/grzegorz-aniol/ffleet-dist

Download the build for your platform from there, put it on your PATH (e.g. ~/.local/bin/ffleet), make it executable, and verify it the same way with ffleet version.

That repo ships binaries only — no source. It's also where you report issues (see Feedback).

Or install with Homebrew (macOS and Linux)

If you use Homebrew, the tap installs and updates the same prebuilt binary for you:

$ brew install grzegorz-aniol/tap/ffleet

Shell completion (optional, recommended)

Enable tab-completion for commands and options:

$ ffleet --install-completion