Home

Forge Fleet

Forge Fleet (ffleet) spins up isolated, containerized coding-agent environments — one per branch. Because each is a real git worktree, you can stack them: start a new environment from a branch that itself came from another environment's branch. It wraps the underlying moving parts (git, Docker, tmux, and the coding assistant) behind a single lifecycle and makes each environment visible and easy to reason about. Today it drives Claude Code and OpenAI Codex. Nothing forces a specific use: the work doesn't have to be complex programming, and — with --here / git-mode off — it can even run without git version control at all.

Each project's settings live in a per-project ffleet.toml written once by ffleet init (by default under the ~/.forge-fleet workdir), so you configure a project once instead of re-passing CLI flags every run — see the config reference.

Documentation

Start at the top and stop when you have what you need.

• 0. Install — host prerequisites, accounts/auth, installing ffleet (Homebrew or manual binary).
• 1. Basic flow — the shortest route to value: init → up → check → remove.
• 2. Concepts — shared vocabulary: slug, and the core idea that up is state-driven, not flag-driven. Contains the two anchor diagrams (state machine + lifecycle overview).

How-to (use-case driven, one per lifecycle stage):

• Starting an environment — prompts, in-place mode, coding-assistant and git-mode selection, worktree placement, templates.
• Working with a running environment — attach/detach, goto, ls/status/tail/path, stop + revive, tmux, what can and can't change mid-life.
• Completing / cleanup — remove, and the ~/.forge-fleet project registry (project ls/prune/rm).

Reference (full detail — the how-to pages link down to these):

• Command reference — every command and flag (generated from --help).
• Config reference — every ffleet.toml setting.

Advanced topics:

• Docker outside Docker (DooD) — using Docker from inside an environment (we do not support Docker-in-Docker).
• Templates — full templates guide and PM-tool integration (GitHub Issues, Linear).
• Secrets & keys — the three mechanisms (docker_env_file, copy_files, extra_mounts) and when to use each.
• Container configuration — volumes/mounts, credential dirs, extra_hosts, image selection.
• Config precedence — CLI flags vs ffleet.toml vs defaults, and why some settings only apply after remove.

Troubleshooting — diagnose with status/tail, recover with stop + up.

License

Forge Fleet is proprietary freeware: free of charge, closed-source, and licensed, not sold. You may install and use it for any purpose (including commercial) on any number of machines, and redistribute it complete and unmodified at no charge — but you may not modify, reverse-engineer, resell, or sublicense it. It is provided "as is", with no warranty and no liability: Forge Fleet automates Docker containers, git worktrees, and git branches and can delete them, so you are solely responsible for your data and for keeping backups. See LICENSE.txt for the full terms, which govern.

Feedback

Report issues on the public binaries repo: ffleet-dist. That repo ships binaries only, no source; the project is closed-source freeware, and we may be selective about what we take on.

Support us

Forge Fleet is free. If it saves you time, you can buy us a coffee — entirely optional. ☕

In the meantime: Buy me a coffee → buymeacoffee.com/appga