Skip to main content
Settings are where the local-first runtime becomes usable for a specific team. The job of this section is not to list toggles. It is to make the important runtime assumptions explicit and predictable.

Make runtime assumptions visible

Good settings surfaces do not bury important routing details. They make editors, agents, MCP bindings, repository metadata, and remote path assumptions explicit enough that a team can operate without guessing.

Editor defaultsAgent profilesMCP bindingsRemote paths
Conductor project context

General Settings

Tune editor behavior, UI preferences, and other daily-use defaults without hiding critical runtime assumptions.

Agent Profiles

Standardize how different repositories route through different coding agents and model profiles.

MCP Servers

Scope shared and project-specific MCP tools without turning the runtime into one giant global config blob.

Projects and Remote Paths

Keep repository metadata, SSH-aware development, and task-routing state clean as teams scale out.

Settings areas

Last modified on March 6, 2026