Skip to main content
Settings opens with ⌘, and is organized as panes down the left, in this order: General, Sessions, Loop, Project, Streams, Notifications, Mobile, MCP, Storage, Edge, and Pro & Dev. Two of them appear only when they apply: Streams needs Edge plus its Loop intake switch, and Mobile needs Pro. Edge is listed on every channel, because it is the only place to turn Edge on. Almost everything here is a default for new work. Changing a default never reaches back into a session or a piece that is already running. Two panes are worth knowing about before the rest. Sessions and Loop hold separate defaults for the two kinds of work, so a change in one does not affect the other. Project overrides either of them for a single project. Where defaults live explains which one wins.

General

Grouped into Getting Started, Interface, Power, Updates & Privacy, and Integrations.
The two privacy rows are the same two choices the first-run notice offers, worded identically. See Privacy and data for what each one sends.

Sessions

Defaults for standalone sessions, the ones you start on the Canvas. Grouped into Model, Defaults, Worktrees, and Experimental.
Fermata Settings open on the Sessions pane, showing Default Model, Model Provider, Default Permissions, Open Sessions In, and the Git Worktrees toggle

The Sessions pane: the model, the provider card, the permission default, and the worktree conventions shared with pieces

Loop

Defaults for pieces: the model, how hands-off a run is, and how many agents may run at once. Grouped into Model, Execution, Autonomy, Interview, and Lifecycle.
Fermata Settings open on the Loop pane, showing Default Model, Default Effort, Limits, Piece Permissions, and the Require Plan Approval, Require Review Before PR, Run Code Review Before PR, and Run Work Review After Agents toggles

The Loop pane: the piece model, the agent limits, the permission default, the gates, and the passes

Piece Permissions is deliberately not the same control as the Sessions pane’s Default Permissions, and it starts on a looser setting. See how much happens without you for why.

Project

Per-project overrides. Every card inherits the global default until you switch the override on, and the card shows you what it is inheriting. The concurrency ceiling, your account, sync, and app-wide preferences stay global.
The Project tab's Branch Behavior card with the Base branch menu open, showing Auto-detect · main followed by the repo's other local branches

The Project tab's Branch Behavior card: the Base branch menu with Auto-detect and the repo's local branches

Streams

Appears only with Edge on and its Loop intake switch on.
Stream Sources are the accounts Fermata reads issues from; keys stay in your Keychain. The “Connect an account” row has Linear… and GitHub…; each connected account is a row naming the kind and the account (“Linear · Acme”) with a health line, and its menu has Check now and Disconnect account…. With a project picked in the scope switcher, the pane leads with that project’s Streams and splits the accounts into the ones this project reads and “Other accounts”. With “All projects” picked, it also carries Check for new issues every, the interval for Stream checks. See Connect Linear and GitHub and Add a stream.
The Streams pane in Settings with a Linear row and a GitHub row, each showing a health line, Check now and Remove, and the Connect Linear and Connect GitHub buttons below

Settings → Streams: the accounts Fermata reads issues from

Notifications

Mobile

Appears once the companion is available to your account.
Pairing for the phone companion: Generate Pairing QR Code, then scan it from the phone. Once paired, the pane shows the device name, live sync health, an “End-to-end encrypted” confirmation, and Unpair. See The phone companion.

MCP

The pane appears on every channel. The server is off until you turn on MCP server, and the rows that depend on it stay greyed out until then.
The Preferred port field defaults to 8787: type a port and press Apply. Fermata tries that port first, then the next nine, then whatever the system offers; a port change takes effect at the next start or Retry, never underneath a call already in flight. Once the server is running, the pane shows the bound host and port, a health readout, and whether Claude Code currently has the server registered. The “Endpoint” card carries Register (or Unregister) and Regenerate Token. The “Connect a client” card switches between three methods, One-off, Shell alias, and Register, and its “Copy” row has Instructions and Inline Config. See connect a client.

Storage

Edge

The channel switch, Enable Edge features, and a “Features” card with one switch per preview feature: Code review, Web diff viewer, Loop intake, and Cost ceiling. See Edge features.
Settings' Edge pane: the Enable Edge features toggle at top and the Features card below listing Code review, MCP control plane, Web diff viewer, Loop intake, and Cost ceiling with a Pro badge

Settings → Edge: the channel switch and one switch per preview feature, Cost ceiling marked Pro

Pro & Dev

“Current Tier” reads “Free” or “Pro”. Free is the whole desktop app, and nothing here is required for normal use. Pro is unlocked by an “Invite Code” during the phone companion’s beta. It turns on the companion and the sync it runs over, the spend insights cards on Analytics, and the cost ceiling behind Edge. See the phone companion. The Edge switch is not here. It has its own pane, described on Edge features.
The Pro and Dev pane of Settings showing Current Tier reading Free and an Invite Code field with an Activate button

Pro & Dev: the current tier and the invite code