Fleet is deliberately thin about what it provides. It runs tools you already have, with credentials you already hold.
macOS on Apple silicon
Fleet ships as an Apple silicon build. There is no Intel build, no Windows build and no Linux build, and none is planned as a translation of this one.
git
Any recent git. Fleet uses worktrees, which have been in git for a long time, but it also expects
git worktree to accept -- style paths and to prune cleanly, so do not run something ancient.
Claude Code, authenticated
Fleet does not bundle a model, does not proxy one, and holds no Anthropic credentials. It drives your Claude Code installation and your usage is billed to your own account.
claude --version
If that does not resolve, install Claude Code and authenticate it in a terminal. Fleet's Setup pane will hand you the command.
Fleet excludes the Claude Code binary from its own bundle on purpose. The Node SDK ships it as a 257 MB optional dependency, and shipping a second copy would mean the app disagreed with your terminal about which version you were running.
GitHub CLI, for pull requests
gh is optional and only needed for the parts of Fleet that talk to GitHub: opening a pull request,
reading its checks and its review state, and cloning from an organisation. Everything else, including
branching, committing and merging locally, is plain git.
gh auth status
What Fleet does not need
- No account. There is nothing to sign up for and nothing to log into inside Fleet.
- No network, most of the time. Fleet itself makes exactly one request on its own behalf, the
update check, and you can turn it off. Everything else on the wire is Claude Code, git,
gh, or something an agent chose to run. - No Docker, no VM, no sandbox image. Isolation here is a git worktree and a separate process, not a container. Agents run with your privileges. That is the trade, and it is worth knowing about before you reach for Bypass mode.
Checking all of it at once
From a checkout of Fleet's own repository, make doctor runs the same preflight the app does: node,
git, claude and its authentication, gh and its authentication, and the login shell PATH.
PATH is the one worth naming. A GUI-launched .app on macOS inherits a minimal PATH that contains
neither gh nor claude, so Fleet resolves your login shell's PATH once at startup. If a packaged
build claims a tool is missing that your terminal can see, that is the mechanism to suspect.