Settings
The single write surface for configuration — every tab, what it edits, and when a change applies.
Settings is the one place configuration gets written. It is deliberately the only view that cannot pop out into its own window — one window, one writer, no racing edits. Everything it saves lands in a file under your install root or your per-user application data; the configuration reference maps every file and key.
The one idea to carry into every tab: where a setting lives decides when it applies. Secrets and wiring are restart-bound — save, then restart the affected service (Dashboard ▸ Platform Health). Runtime knobs are hot — they apply on the next operation with no restart. Each tab below is labeled accordingly.
The tabs
A left rail lists the tabs; the pane on the right shows the active one.
Account
Desktop sign-in and your plan state. Sign in, refresh your entitlement, or sign out; the tab also shows which modules your tier unlocks — a locked module shows a lock panel in place of its view. Gating here is coarse by design; see tiers for what Pro and Ultra include. A Privacy & data card states what the app stores locally and what leaves your machine.
Project
The workspace root — the folder tree the whole platform operates on. Set at first run by the wizard; change it here only deliberately, since every view and daemon resolves paths against it.
Database
The knowledge-graph backend behind Cortex. Choose between the
provisioned-local server the app runs on 127.0.0.1 (no extra installs)
and an external instance you host yourself, and manage the connection
settings for either. The backend choice itself is a hot setting; agent
sessions pick up a switch after the agent tooling restarts, and the tab spells
out what applying costs. See the knowledge graph.
API Keys
The model and service keys the platform uses. Restart-bound: keys live in the environment file, and the panels only ever report whether a key is set — the values stay on your machine. Doctor has dedicated rows that tell you which capabilities are waiting on which key.
Integrations
Credentials and endpoints for the outbound and harvest integrations (email, X, newsletter inboxes). Restart-bound, same as keys.
Daemons
The endpoints and ports of the background services. Defaults are correct for a standard install; this tab exists for the day you need to move a port. Restart-bound.
Doctor · MCP Servers · Data Layer
Three full system surfaces folded into Settings as tabs. Each renders its complete view here and has its own guide: Doctor (health checks with fixes), MCP Servers (the tool servers agent sessions load), and Data Layer (your local stores and their backups).
Paths & Outputs
Relocate where each output tree is written — rendered videos, generated images, exported products, harvested reports. Hot: stored in the runtime config, read by the owning service on its next write. Blank means the default location under the workspace root.
Speech-to-Text
The system-wide dictation setup — engine, models, and the push-to-talk behavior toggled from the title bar.
Terminals
The behavior of the Terminals workspace and the agent control planes:
- Agent control planes — the enable gates for agent-driven terminal control and window control. Flipping a switch takes effect immediately and persists to the runtime config. Each plane also has its own runtime pause and audit log; the terminal plane can run shell commands, so treat it as the more powerful of the two.
- Mission fleet + lint — the fleet worker cap and mission-lint thresholds. Hot: re-read fresh on every fleet operation. Blank means the built-in default.
- Session resume — whether agent terminals automatically reload the exact conversation they were running when the app restarts. Capture always runs; this switch only controls automatic resume, and a workspace's context menu offers Resume sessions on demand.
- Drag to reorder — how pane docking behaves when you drag panes, and how wide the dock zones are.
Activity Log
The retention window for the durable activity store — how many hours of events the Activity Log keeps before the hourly cleanup removes them.
Updates
Command Center checks for updates automatically at launch and every four hours; this tab adds a manual check and shows the current version. An available update offers a one-click restart-and-update. See how updates work.
Themes
The full theme picker — all six themes as swatch tiles. The sidebar footer carries a quick switch with the three pinned themes; this tab is where the rest live.
After you change something
- Hot tabs (Paths & Outputs, Terminals, Themes, Activity Log) — done; the change is already live or applies on the next operation.
- Restart-bound tabs (API Keys, Integrations, Daemons, Database connection details, Project) — restart the affected service from Dashboard ▸ Platform Health; agent sessions pick the change up on their next launch.
- Not sure it took? Run Doctor — it verifies keys, config, daemons, and the database against what you just changed.
Related pages
- Configuration reference — every file, every key, every reload cost
- Doctor — verify a configuration change end to end
- How updates work
Doctor
The health board — every dependency, daemon, and configuration probe in five groups, with one-click fixes on the rows that fail.
Agentic infrastructure
The working surface beneath the views — the tool fabric, the agent roster, skills, routines, memory, the knowledge graph, the daemons, and the doctrine that governs them.