Settings and maintenance

Saggar's defaults favor a quiet, recoverable workspace. Settings lets you change how it looks, what earns your attention, how long terminal state stays on disk, and which integrations may edit files outside the app.

Finding a setting

Open Settings with ⌘,. Its sidebar is searchable, including words that do not appear in a pane title: “hooks” finds Providers, “scrollback” finds Terminals, and “split pane” finds Interface. The panes are grouped as App, Workspace, Agents, and Access.

Appearance

A theme family pairs a light and dark palette with a window material. Saggar can follow macOS automatically or stay on either appearance. The ceramic families may add a photographic texture and slow palette-colored light drift; turn Show image backgrounds off to keep the same palette on a plain surface. Custom mode lets you choose the light and dark palettes independently.

App text and terminal text have separate sizes. The app control scales Saggar's menu, cards, panes, and palette; macOS still draws standard controls and menus at the system size. Terminal settings choose any installed fixed-width font, set a separate point size, and decide whether the terminal canvas follows the app's appearance or stays dark for tools whose dim colors assume a dark background.

Interface

Monitor settings choose the default card size, whether new monitors start collapsed, and whether idle monitors fade until hovered or needed. The discreet project menu does the same for the left side of the main window. Quick Runs may start tucked into their project row.

Monitors follow their project. Quick Runs and split panes do too by default: leave a project and they hide, then return when you come back. Interface settings can keep either one visible across project changes when your workflow needs a fixed companion.

Notifications, sound, and watch patterns

Notification Center banners, command-completion notices, menu reordering, program-raised notifications, sounds, and trackpad feedback each have their own controls. Individual sounds can be disabled or previewed, and sound effects can be limited to the time Saggar is in the background.

Programs inside a terminal can raise titled notifications through OSC 99 or OSC 777, including over SSH and from containers. Urgent messages make the terminal need you. Watch patterns add your own plain-text or regular-expression cues to the same vocabulary, which is useful for log tails and test watchers. The optional away summary collects what finished, failed, waited, or stayed dirty while you were gone into one card when you return. Saggar can also compact an idle Claude chat once you have been away for 30 minutes and its context is at least half full; it records confirmed compactions in that return summary.

Projects and terminals

Projects settings choose the default editor, control smart collapsing, and manage the folders Saggar scans for Git repositories. Scanning walks a few levels beneath each root and stores the list in ~/.saggar/config.json.

Terminals settings create reusable terminal definitions, enable OSC 133 shell integration for exact command boundaries and exit codes, choose the live scrollback depth, and control paste, close, and quit warnings. A timed tidy can close terminals that have gone quiet, but it protects waiting prompts, live commands and processes, failures, and every terminal currently shown in a pane, monitor, or separate window.

Scrollback restoration stores snapshots under ~/.saggar/scrollback. Turning it off deletes those snapshots. Project History retention is separate and can keep closed terminals by count or age. See Projects and terminals for how restored and closed sessions appear.

Agents and Turbo

Providers chooses the agent CLIs shown in launch menus, reveals older or less suitable models on request, and manages each provider's handshake and Saggar skill. It also controls whether an agent may run saggar approve inside its own terminal. Destructive approvals still stop for you. Installation always names the external config or skill file it will change.

Turbo settings choose which providers start armed and show every destructive-command category Turbo refuses. Built-in protections can be disabled individually, and your own plain-text or regular-expression rules can hold additional commands for review. See Agents for the provider contracts and Turbo's safety model.

General maintenance

Launch at login

Registers the packaged app with macOS. Development builds cannot.

Command line

Installs saggar under ~/.local/bin and updates the profile for your configured login shell. saggar . then adds or focuses the enclosing repository.

Welcome

Runs the first-launch tour again without resetting the app.

Diagnostics

Reveals or exports app details, logs, and crash stacks. The bundle excludes terminal input and output, commands, account data, and tokens. Automatic crash sharing is on by default and sends only coarse Mac details and sanitized crash stacks. It never sends file paths, environment variables, screenshots, traces, or profiles.

Reset

Restores every preference to its default without removing the account, pairings, projects, terminals, history, watch patterns, or custom Turbo rules.

Updates

Saggar checks its small release manifest at most once a day and stays silent when the installed version is current or a background check fails. When a release is available, a banner offers the right path for the installation: a visible Homebrew upgrade in a monitor, or the download page for a direct install. Check for Updates… in the app menu runs the same check immediately and reports success or failure.

Language

Saggar follows the language order in macOS. The app is localized in English, French, German, Spanish, Simplified Chinese, and Traditional Cantonese. Use System Settings ▸ General ▸ Language & Region ▸ Applications when Saggar should use a different supported language from the rest of the Mac.

Account and remote access

The Marginal Utility account pane signs the Mac in or out and opens account management in the browser. Remote control settings choose whether the Mac dials the relay, control the idle-sleep hold, approve pairing requests, revoke devices, and show recent remote actions. The remote-control documentation covers those security-sensitive controls in full.