Forge Fleet

// isolated agent fleets

Forge a fleet of AI coding agents.

Each sealed in its own container. Local-first, free for everyone — no cloud VMs, no agent with a shell on your host.

$ Get started Why Forge Fleet

Real isolation, not just parallelism.

Every rival fans out agents into parallel git worktrees — and runs them straight on your host. Forge Fleet adds the one layer none of them do locally: a container around each agent.

  • Primary

    # Real isolation, per agent

    Every agent runs in its own Docker container — the one thing no competitor does locally. Give agents full autonomy (e.g. --dangerously-skip-permissions) safely; a mistake stays in the box, never on your host.

  • # Local-first, no cloud lock-in

    Runs entirely on your own hardware. No cloud VMs, no code leaving your machine, no vendor account required.

  • Secondary

    # Scriptable & agent-drivable

    Forge Fleet ships an MCP server, so a lead agent can spawn and drive isolated worker agents — the safe sandbox substrate under multi-agent systems.

  • # Parallel worktrees + containers

    One isolated git worktree and one container per task, managed through a single up-driven lifecycle in your terminal (tmux panes).

Get started

Forge Fleet is Docker-native by design. You need three things on your host before the first up:

  • git
  • docker
  • the forge-fleet:latest image — bundles claude, codex, and tmux

macOS and Linux. Docker is a hard prerequisite — that container is what makes the isolation real.

install 
# 1 — install the CLI
$ brew install grzegorz-aniol/tap/ffleet

# 2 — launch an isolated agent
$ ffleet up feature-login