Configuration
Where Fleet keeps its settings and session state, and what you can change by hand.
The two files
Fleet writes everything to ~/.config/fleet-terminal/.
config.json — settings
Theme, font, cursor style, terminal behaviour, which sidebar fields to show, notification rules, AI options. Everything here is editable from the searchable Settings panel (⌘,), which is the recommended route — but the file is plain JSON if you would rather edit it directly.
state.json — open sessions
The sessions you had open, and for each one its working directory, custom name, colour, group and position. This is what gets restored on launch.
Sidebar fields
Each info chip on a row is individually toggleable under Settings → Sidebar:
- model — the Claude model in use
- ctx% — context window used, coloured green under 70%, amber under 90%, red above
- mode — the current permission mode
- ⚙ subagents — how many subagents are running
- branch — the git branch of the session’s working directory
Turning them all off leaves a clean title-and-status row.
Attention routing
Under Settings → Notifications:
- Float waiting sessions to the top reorders the sidebar so anything blocked on you rises above the rest
- Per-state toggles let you notify on permission prompts but stay quiet for, say, PR-opened
- Per-session mute silences one noisy session without changing the global rules
- Distinct sounds map different states to different alert sounds
Notifications for permission prompts carry Approve and Deny buttons, so you can unblock a session without switching to it.
Launch profiles
A profile is a saved starting point — a working directory plus the command to run. Combined with New in Folder…, this is the fast path for a many-worktrees workflow: one profile per worktree, each opening a Claude session in the right place.
Find them under the ▾ menu on the sidebar’s + button.
Resource bar
Settings → Appearance → Show resource bar adds a strip showing CPU, RAM,
network and process count across Fleet’s whole process tree, with a per-session
breakdown on click. It is sampled with ps and nettop, and it is off by
default.
Re-running onboarding
Set onboardingSeen to false in config.json, or use
Help → Welcome to Fleet.