Chorus—
New chat
Recent

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.

## Sandbox & first-call permissions

What can chorus-spawned reviewers do on this machine? Pick a profile, toggle prompt auto-approval, choose whether to allow outbound network.

Open Permissions page→

## Run mode (headless / tmux)

How chorus runs each CLI. Default is headless (faster, lower RAM). Switch to tmux if you want to attach to a live voice and take over mid-run (debug + handoff).

Tip: set `CHORUS_TRANSPORT=tmux` in your environment to override per-shell without changing this setting.

## Concurrency

Max parallel CLI subprocesses across all chats. Caps memory pressure when stacking heavyweight reviewers.

Loading…

## Chat concurrency

Max chats fanning out at once + resource-pressure guardrails.

Loading…

## Billing mode

How you pay for the AI CLIs chorus drives. Affects what the cost preview shows on the new-chat page — defaults to API rates so the number stays honest until you tell us otherwise.

## Anonymous telemetry

A small heartbeat sent to chorus.codes once per boot + every 24h. Helps us see what versions / OSes are in the wild. No code, no prompts, no chat content.

Send anonymous heartbeat Sends: install UUID, chorus version, OS, arch, node major, daemon uptime, count of chats in the last 24h. That's it.
Other ways to opt out

- Set `CHORUS_TELEMETRY=0` in your shell — also accepts `false`, `no`, `off`.
- `touch ~/.chorus/no-telemetry` (cargo / brew convention).
- Reset your install ID: `rm ~/.chorus/install-id` — a fresh UUID is minted on the next heartbeat.

Coming in v0.8 — preview only

The sections below show planned controls. They're not wired to the daemon yet — interaction is disabled. The YAML toggle at the top of the page already exposes the schema if you're curious.

## Per-tool auto-approve

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

Tool Driver Reviewer
Read files cat, less, head, file open
List & search ls, grep, find, ripgrep
Write files Edit, Write inside allowed dirs
Run commands Bash, npm, pnpm, python, go
Network access curl, fetch, package install
Writes outside working dir Anything outside the allowed paths below

When wired: `ask` prompts will 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.

Default driver
Default agreement threshold
Default cost cap (USD per chat)
$
On model error

## 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.

Webhook URL (optional)

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