Fleet runs Claude Code sessions on your Mac, each one isolated in its own git worktree, driven from
a window instead of a terminal. It does not host anything, it has no account, and it uses the
claude you already have installed.
Before you start
You need macOS on Apple silicon, git, and your own authenticated Claude Code. For pull requests you also need the GitHub CLI, authenticated. The requirements page has the detail and the exact commands.
1. Install
Download Fleet, drag it to Applications, and open it. On first launch you land in Setup, which checks each dependency and tells you what is missing.
Setup never asks you to log in inside Fleet. Both claude and gh authenticate in a terminal, so
Setup hands the command to your own Terminal and waits for you to come back. That is deliberate:
Fleet never loads a remote page into its own window, for any reason, including authentication.
2. Add a repository
Add a repository three ways:
- Add from disk. Point Fleet at a git repository you already have.
- Add from GitHub. Clone one from an organisation you belong to, into your clone root.
- New project. Scaffold a fresh project from a template, commit it, publish it and open a session on it. See projects from templates.
3. Start a session and say what you want
Press Cmd N, choose the repository, and type what you want done.
Nothing happens on disk when you create the session. Fleet makes no worktree until your first prompt, which is why the branch can be named after what you actually asked for rather than after a timestamp you would have to decode later. Sending the prompt is what provisions the worktree, creates the branch, runs the repository's setup script if it has one, and starts the agent.
4. Pick how much it may do without asking
Every session runs in one of four modes, and you can change it mid-session:
| Mode | What it means |
|---|---|
| Plan | Research and propose only. No edits, no commands. |
| Ask | Approve every tool use. |
| Auto | File edits apply without asking. Commands and anything outside the worktree still prompt. |
| Bypass | Nothing asks. |
Auto is the one worth understanding properly, because the line it holds is containment rather than tool type. See permissions and modes.
5. Review the diff, then ship it
The review panel shows the session's whole diff against its base: everything committed on the branch plus everything not committed yet. You can select lines and leave notes, and send those notes back to the agent as one prompt rather than retyping them into chat.
When you are happy, merge into the base branch from the main worktree, or push and open a pull
request with gh. See review and merge.
Where to go next
- Your first session, walked through in full.
- Worktrees and branches, for what Fleet is doing to your repository.
- Squads overview, when one agent is not enough.
- If any of this is new, Learn teaches the underlying ideas from scratch.