Settings
System & data
Sync, teams, the harness, hooks, the CLI, privacy, and your local data.
The System group holds Operon’s plumbing and your data controls: how work mirrors to the cloud, your team workspace, the safety harness, where hooks are registered, the operon CLI, the MCP server, telemetry, and the export/clear controls for your local data. Most of it can be left at its defaults — but this is where you go to tune how Operon behaves and to take your data with you.
System settings at a glance
| Section | What it controls |
|---|---|
| Sync | Cloud sync on/off, sync level, and connected devices |
| Team | Create or join a team to share sessions and dashboards |
| Harness | Checkpoint gate and agent-safety defaults |
| Hooks | Whether hooks register globally or per project |
| CLI | The operon command and adding it to your own shell |
| MCP Server | Expose Operon data to Claude Desktop and other MCP clients |
| Privacy | Opt-in anonymous crash reports |
| Data | Export everything, clear everything, and where data lives |
| About | Version, device ID, and checking for updates |
Sync and sync levels
Sync mirrors your session metadata to the cloud so it is available on your other devices and, for teams, to collaborators. It is opt-in and requires signing in. When you are not signed in, this section simply invites you to sign in; there is no cloud dependency in local mode.
Note
At the default sync level, more than metadata syncs — traces, decisions, tasks, plus prompt/response text, tool inputs/outputs, and code diffs. Turn off the code-content toggle per project to stop diffs and tool I/O from syncing. Your repository is never uploaded as files. The API key and your settings never leave the machine.
The sync level lets you choose how much metadata mirrors up. Lower levels share less; Off pauses sync entirely.
| Level | What it mirrors |
|---|---|
| Full | The full set of syncable session metadata. |
| Decisions | A narrower set focused on decisions and outcomes. |
| Observe | A minimal, observation-only slice. |
| Off | Nothing syncs while this is selected. |
This section also offers Sync Now to push immediately and a Force Full Resync for the rare case where the web app shows missing sessions after a plan change — it re-uploads all local data.
Team
The Team section is where you create a team or join one, and where you see your current team and role. A team workspace is what lets sessions, decisions, and cost dashboards be shared with collaborators. Managing members and invites opens the fuller team settings surface.
Harness
The Harness section sets defaults for Operon’s active-control features. The headline toggle is checkpoint gates: when on, completing a Flight Plan step creates a git-tagged checkpoint and pauses the running tool so you can review the diff and confidence score, then approve, reject, or roll back. When off, plan steps advance without interruption. Changes apply to the active session immediately and to every session you open afterwards.
Important
The Harness also has an advanced pre-accept bypass for auto-run claude-code agents. It is off by default and, when enabled, makes a machine-global, persistent change to your ~/.claude.json. Leave it off unless you specifically need it for auto-run agents such as Arena seats.
Hooks
Hooks are how Operon captures rich, structured data from Claude Code and other supported tools in real time — tool usage, sub-agents, and responses. The Hooks section shows whether the hook receiver is running and lets you choose where hooks are registered.
| Scope | Registered in | Applies to |
|---|---|---|
| Global | ~/.claude/settings.local.json | Every project on this machine |
| Project | .claude/settings.local.json | Only the current workspace |
After changing the scope, use Re-register Hooks to apply it. Cleanup All Hooks removes Operon’s hook entries from both the global and project files if you want to start clean.
CLI
Operon ships a small command-line tool, operon, that lets an agent drive Operon from inside its own terminal — checking session status, tailing traces, and using the coordination bus. Sessions started from inside Operon already have operon on their PATH, so there is nothing to set up for them.
If you want to use operon in your own separate terminals too, the CLI section offers a one-click opt-in that adds a small, clearly marked, removable block to your shell config pointing at ~/.operon/bin. It only ever touches Operon’s own block — it never edits configuration it did not write — and you can remove it just as easily. Open a new terminal after adding it for the change to take effect.
MCP Server
The MCP Server section exposes Operon’s own data — sessions, traces, decisions, projects, and tasks — to any MCP-compatible client such as Claude Desktop or Cursor. It shows the server status, the database path it reads from, a copy-ready config snippet for Claude Desktop, and the list of tools the server provides.
Note
The server status may read "Not Built" instead of "Ready". That is a valid state, not an error — in some builds the MCP server component is not compiled in. If you need it, build the app from source so the server is compiled, then it will report Ready. This has no effect on the rest of Operon.
Privacy
Privacy controls anonymous crash reporting. It is off by default and fully opt-in. When you turn it on, Operon sends only app version, platform, error codes, and durations — never your prompts, file paths, or team data — and the payloads are scrubbed for secrets before they leave. Reporting can also be hard-disabled by an environment variable, in which case the toggle shows as disabled and nothing is sent regardless.
Data
The Data section is your export and reset panel. Export downloads all your sessions, traces, and decisions as JSON — scoped to your own data — so you can back it up or move it elsewhere. Clear All Data permanently deletes your local sessions and traces after a confirmation; there is no undo.
Tip
Operon keeps its local data under ~/.operon in your home directory — the SQLite database, config, keychain-migrated secrets, and backups all live there. Back up or inspect that directory if you want a full copy of your local state.
About and updates
The About section shows the app version, your platform, and this device’s ID (which you can copy for support), plus links to the project and docs. It is also where you check for updates: click Check for updates and Operon looks for a newer release, downloads it when available, and offers a Restart & Update button when the update is ready to install. Release notes for the pending update are shown inline.