Download

Fleet for Mac. Free, local, no account.

A squad of Claude Code agents, each in its own git worktree, on your own machine. This is the app on this page: no sign in, no server, no telemetry, and the only request it makes on its own behalf is the update check. Fleet workspaces, the hosted service, is a separate product you opt into and it changes nothing here.

Download for macOSv0.19.0 · 131 MB

Apple silicon. Intel Macs are not supported.

version: 0.19.0
released: 2026-08-13
sha512: VZfXTlYXGFI36Gjz0CMcPHx4w8rEG7Ltu+T6OPYYqqcgsgn+ED7KMTAzReT2zmWSpabluAx2a2U4yEOeE3aJDQ==

Trust

Your code stays on your machine.

The agent runs with your filesystem privileges, which is the point and also the risk, so the boundaries are worth reading before you install rather than after.

Nothing leaves

No account, no server holding your repositories, no telemetry, no analytics in the app. Fleet talks to Anthropic through your own Claude Code and to GitHub through your own gh. A hosted workspace is the only thing that changes any of this, and you have to ask for one.

A display layer that stays one

Context isolation on, sandbox on, node integration off, a content security policy, and navigation blocked. No remote URL is ever loaded into a Fleet window, including for auth.

Repository content is untrusted

Markdown from a repository renders without raw HTML, so a README cannot smuggle an element into the window that is reading it.

Commands by id

The commands Fleet can hand to your Terminal live in a main process allowlist and are chosen by id. A free text command from the display layer would be a straight path to a shell.

Requirements

What you need.

Mac: Apple silicon. Intel Macs are not supported, and there is no Windows or Linux build.
Claude Code: Your own install, authenticated with a subscription or an API key. Fleet ships no copy of it and never asks you for a key.
GitHub CLI: gh, authenticated. Fleet uses it to open pull requests. Everything else works without it.
Git: A repository with a remote. Fleet fetches from it and never pulls your base branch.

First launch

What to expect the first time.

Setup checks what is on your PATH

Fleet resolves your login shell PATH at startup and probes for claude, gh and your editors. Anything missing is named, with the command to fix it.

Logins happen in your Terminal

claude and gh both authenticate interactively, and Fleet will never load a remote page in its own window, so it hands the command to Terminal instead. The commands it can hand over are a fixed list chosen by id.

Add a repository, or create one

Point Fleet at a repository on disk, clone one from an organisation, or scaffold a new project from one of 30 templates. Nothing is copied anywhere, and Fleet works against the repository where it already is.

The first prompt makes the worktree

Creating a session makes no checkout at all, so the chat opens instantly and the branch can be named after what you actually asked for. The first prompt is what provisions it.

Fleet reads the repository’s own CLAUDE.md, its .claude/settings.json and its slash commands, so a session behaves the way your terminal does on the same repository rather than like a different tool.