Settings

Workspace

Defaults applied to every chat. Templates can override these per-run. The MCP server can read & patch this config — your main Claude can configure Chorus for you.

Concurrency

How many chats Chorus runs in parallel. Overflow waits in a queue.

1510
3 concurrent

Each chat reserves one tmux session + 9 reviewer panes. Above this limit new chats land in a FIFO queue.

Permissions & auto-approve

Drivers write code; reviewers don't. Defaults reflect that. Click any chip to cycle auto / ask / block.

ToolDriverReviewer
Read filescat, less, head, file open
List & searchls, grep, find, ripgrep
Write filesEdit, Write inside allowed dirs
Run commandsBash, npm, pnpm, python, go
Network accesscurl, fetch, package install
Writes outside working dirAnything outside the allowed paths below

ask prompts appear as cards in the chat — you click Approve / Deny instead of the agent stalling.

Working directories

Each tmux session is started inside one of these paths. Writes outside are blocked.

~/dev~/work/tmp/chorus-sandbox

Template defaults

Applied to new templates and one-off chats. Per-template values override these.

$

Privacy & data path

How prompts and code reach each LLM. Affects what leaves your machine.

Notifications & MCP

How outer orchestrators (your main Claude / Cursor session) get pinged when a chat finishes or blocks.

Posted on chat finished / blocked / errored. Payload includes chat_id, status, synthesis.

All changes saved