Getting started
Install Fleet, open your first sessions, and wire up the Claude Code status layer.
Requirements
- macOS 14 or later
- Node on your
PATH— the Claude Code hooks are Node scripts with no npm dependencies - Claude Code, if you want the live status layer. Plain shells still work; they just appear as basic rows
Install
Download the latest build from the download section, move
Fleet.app to /Applications, and open it.
Fleet is signed and notarized by Apple, so it opens with no warning and no right-click dance.
Your first sessions
Fleet opens with a single shell. From there:
- ⌘T opens another shell session
- ⌘⇧T opens a Claude session
- The sidebar’s + New Session button is a split button — click it for a shell, or use the ▾ menu for a Claude session, a specific folder, a saved launch profile, or a new group
Each session gets its own row in the sidebar. Double-click a title to rename it, right-click for colour and group options, and drag rows to reorder them within a group.
Turn on the status layer
Out of the box, Claude sessions look like any other shell. To get live status — working, your turn, needs permission, model, context percentage — install the hooks:
Settings (⌘,) → Claude → Set up Claude Integration
This is also offered on the first-run welcome guide, which you can reopen at any time from Help → Welcome to Fleet.
Hooks hot-reload, so there is no need to restart Claude. See Claude integration for exactly what it writes.
Optional: AI summaries
Under Settings → AI, turn on summaries to get a short plain-English phrase under each working session — “wiring auth middleware” rather than “Running…”.
Fleet shells out to claude -p with Haiku, reusing your existing Claude login,
so there is no extra API key to configure. Calls are throttled and only happen
while a session is actually working.