Quorum Terminal runs your AI coding agents locally and keeps the security boundary in the main process, not the renderer. This page covers how Claude Code permission modes are surfaced per terminal, how the app contains file operations to authorized project roots, which providers it works with, and the privacy posture behind it all.
Claude Code permission modes
Each terminal that runs Claude Code carries its own permission mode, so one agent can stay locked down while another runs more freely in the next pane. The mode governs how much an agent may do — from asking before every change to accepting edits automatically — and Quorum Terminal surfaces the current mode for the active terminal rather than hiding it behind a global toggle.
Cycle through the available modes with ⇧ Tab while the terminal is focused. In some configurations ⌥ M works as well. These keys are sent to the running Claude Code session, so the exact modes and their order come from the CLI itself.
Cycling is per terminal: changing the mode in one session never alters another, so review the surfaced mode before letting an agent run unattended.
Project authorization and path containment
The main process keeps a registry of project roots approved through trusted flows, and every file, git, or terminal operation a renderer requests is checked against it. A path that falls outside an authorized directory — or that targets protected metadata — is rejected before it reaches disk.
To resist symlink escapes, each local path is resolved to its real, on-disk form and confirmed to be a directory before it is trusted; remote ssh:// paths are matched lexically and never touched on the local filesystem. The result: an agent can only read and write inside the project you opened, even if a prompt tries to wander.
Providers and privacy
Quorum Terminal works with three AI providers, each as a terminal-based CLI you bring yourself:
| Provider | Tool |
|---|---|
| Anthropic | Claude Code |
| OpenAI | Codex CLI |
| Gemini CLI |
The app itself runs entirely on your machine. It never receives your code, your prompts, or your usage data — those stay between you and the provider CLI you run. Distribution builds for macOS are signed. Quorum Terminal is macOS-only (macOS 13+); Windows and Linux support is planned for Q4 2026.
Something off on this page? Tell us.