Working in threads
Access presets & approvals
Read-only, Ask, Workspace auto and Full auto — one broker for every provider.
Every provider has its own permission system with its own vocabulary. Synergoi replaces them with one broker: the agent asks, the broker applies your preset and rules, and anything that needs you lands in one inbox — the same way for Claude, Codex, Grok, Cursor, Antigravity and local models.
The four presets
| Preset | What it means (the app's own wording) |
|---|---|
| Read-only | Read the repo. Mutations, network, and extra tools stay off; read-only shell commands still ask. |
| Ask | Prompt before any mutation, shell, network, or extra tool. |
| Workspace auto | Auto-accept in-repo file edits. Still ask for shell, network, and extra tools. |
| Full auto | Auto-run ordinary commands. Destructive git and deletes still stop for you. Requires a one-time per-project confirmation. |
Pick the preset per thread from the pill next to the provider (the green dot), and the default for new threads in Settings › Approvals. Ask is the default; Full auto is never a default and asks you to confirm once per project before it applies.
Where approvals show up
- In the transcript, as a banner on the tool that is waiting, with Approve / Deny and the command or path in full.
- The approvals inbox (⇧⌘A) — every pending request across every thread, child and side-ask.
- Outside the window: a macOS notification, the menu-bar tray count and, if you turn it on, a Dynamic Island-style pill — all from Settings › Approvals › Notifications.
Rules
When you approve, you can also remember the decision as a rule: a command pattern (glob), a working directory, and the repo it applies to. Rules live in Settings › Approvals, are editable, and apply to every provider — so allowing bun test * once covers Claude and Codex alike.
What always stops for you
Even on Full auto: destructive git (force pushes, branch deletes, history rewrites), file deletes outside a plain edit, and anything a rule explicitly denies. There is no "YOLO" mode, and no way to approve remotely — approvals happen on the Mac that runs the code, by design.
Something wrong or missing on this page? Email [email protected].