Skip to main content

Frequently asked questions

What is Saggar?

Saggar is a native Mac terminal manager for people running several shells, development servers, tests, and coding agents at once. It groups sessions by project, tracks which ones are working or waiting, and keeps the sessions that need a decision visible.

Is Saggar an AI coding agent?

No. Saggar runs agent CLIs in real terminal sessions and helps you supervise them. The agent still comes from its provider, uses that provider's account and models, and follows the permissions you give it.

Which Macs does Saggar support?

Saggar requires Apple silicon and macOS 26 Tahoe or later. There is no Intel, Windows, or Linux version.

Which coding agents work with Saggar?

Saggar recognizes Claude Code, Codex, Antigravity CLI, Pi, OpenCode, and GitHub Copilot CLI. Ordinary shells and other terminal programs work too. The depth of status, prompt, resume, and usage integration varies by provider; see the provider comparison for the exact differences.

Does Saggar replace my terminal?

It can. Saggar contains a full terminal and runs your real login shell in your real project directories. It also adds project organization, session status, restoration, split panes, commands, monitors, and agent-aware controls. You can keep another terminal installed alongside it.

How much does Saggar cost?

The Mac app is free and doesn't require an account. Remote control is part of Saggar Pro, which costs £1.99 or $2.50 a month after a free first month and renews monthly until canceled. Canceling Saggar Pro doesn't affect the Mac app. See the pricing page for the current plan details.

Do I need an account?

Not for the Mac app. A Marginal Utility account is required for Saggar Pro, including remote control, settings sync, and optional cloud AI features. Remote devices and the Mac must use the same account.

Does my terminal output leave my Mac?

Not during ordinary local use. Settings, terminal history, scrollback, agent status, and diagnostics stay on the Mac unless you use a feature that sends data elsewhere.

Remote control sends end-to-end encrypted terminal traffic through the relay. Optional session summaries and smart session naming send bounded, locally redacted transcript content to a model provider. Crash sharing is separate, sanitized, and can be turned off. Read the security model and privacy policy for the full boundaries.

Can I control Saggar from my phone?

Yes, with the Saggar iPhone app, available through TestFlight while it is in beta. There is no browser client. Pairing requires the same account on both devices and explicit approval on the Mac. Your Mac must remain awake, online, and running Saggar; remote control has no offline path and cannot wake a sleeping Mac. Start with control Saggar remotely.

Can Saggar approve agent prompts automatically?

Yes, for supported providers, but only after you turn off supervision for that provider and choose the default answers Saggar may use. Saggar keeps risky or ambiguous prompts for you. Pro and Teams add local decision history. See automatic approval before enabling it.

Where does Saggar store its data?

User-wide data lives under ~/.saggar/, with credentials and device grants kept separately in the macOS login Keychain. Project documentation and local workspace files may live in a project's .saggar/ directory. The project storage reference lists each file and whether it should be committed.

What happens if I uninstall Saggar?

Removing the app doesn't delete your project folders. Saggar's own settings, history, snapshots, project metadata, and Keychain items may remain until you remove them separately. If you used remote control, revoke paired devices and cancel the subscription from your account when you no longer need it.

How do I install or update Saggar?

Install it with Homebrew or download it directly from the Saggar website. A Homebrew installation updates through Homebrew; a direct installation opens the current download when an update is available. See getting started for installation steps.

Where can I get help?

Start with troubleshooting. If the problem continues, export a diagnostics bundle from Settings ▸ General and follow report a problem. The bundle excludes terminal text, commands, account data, and tokens.