Most questions about Quorum Terminal fall into two buckets: how the product is built and licensed, and small day-to-day snags. This page answers the common ones and points you to the right panel or setting when something looks off.
FAQ
Quorum Terminal runs locally and never receives your code, prompts, or usage data. The AI tools you run inside it follow their own provider policies.
| Question | Answer |
|---|---|
| Is Quorum Terminal open source? | No. It is proprietary, closed-source software. |
| Does it run on Windows or Linux? | Not yet. macOS comes first (macOS 13+); Windows and Linux are on the roadmap for Q4 2026. |
| How does worktree isolation work? | When you launch a multi-agent workspace, Quorum Terminal can create detached Git worktrees under ~/.frame/worktrees, so each agent terminal writes to its own checkout. |
| Will it create branches for me? | No. Branches are never auto-created. |
| Do you train on my code? | No. Quorum Terminal never receives your code, prompts, or usage. |
Common issues
-
macOS permission prompts. On first launch macOS may ask for access to folders, files, or accessibility. These prompts come from the operating system, not Quorum Terminal — grant access to the folders you want to open, and reopen the project.
-
A blank terminal. A terminal hosts your default
$SHELL, so it stays empty until you run something. Press⌘ Kto start the selected AI tool, or just type a command. Use⌘ ⇧ Tfor a new terminal and⌘ ⇧ Nto split the active one. -
Claude Code's
Option+key shortcuts don't register. Those provider shortcuts need the terminal to sendOptionasMeta. Quorum Terminal enables this by default underSettings → Terminal → Option as Meta key. Turn it off only if you needOptionto type accented characters in the terminal. -
Cleaning up worktrees. Open the source-control panel with
⌘ ⇧ Gto review changes per checkout before you remove a worktree. Quorum Terminal places its worktrees under~/.frame/worktrees; since it never auto-creates branches, removing a worktree leaves your branch list untouched. -
Finding logs. Reproduce the issue, then capture what each terminal printed. The source-control panel (
⌘ ⇧ G) shows what changed on disk, and the history panel (⌘ ⇧ H) lists your past prompts with timestamps — both help when you are retracing a session.
Something off on this page? Tell us.