Settings and Appearance
Settings has seven current sections. Configuration is profile-local unless a section explicitly says it is browser-local or runtime-only.
| Section | Current controls |
|---|---|
| Appearance | Light, Dark, or Tinted theme; interface scale; palette family. |
| Behavior | Maximum tool-call rounds and primary workspace root. |
| Providers | Cloud/OpenAI-compatible service, endpoint, and write-only credential; link to Models. |
| Runtime | Redacted configuration evidence, local Ollama process controls, endpoint, and launch settings. |
| Tools | Durable built-in tool availability and web-search credential. |
| MCP Servers | External server definitions, enablement, refresh, and removal. |
| Shortcuts & About | Keyboard controls and application information. |
Models owns defaults, model lifecycle, and observed model evidence. Machine owns current runtime and hardware evidence. A value saved in Settings does not prove reachability or residency.
Appearance
Theme and palette changes apply immediately and are stored for this browser origin rather than in the Pioneer profile.
Canonical palette families are Pioneer, Volt, Aurora, Ember, Monochrome, Terminal, Jaxon, Venus, and Bloom. Each supplies three semantic roles:
- Primary for the main product accent;
- Bridge for related intermediate emphasis; and
- Secondary for complementary emphasis.
Success, warning, error, and information colors remain operationally invariant. Changing to Bloom or another family does not recolor a failed run into a decorative palette meaning.
Behavior and authority
Workspace changes apply to file, search, and Git tools. Setting a custom root applies immediately. Use default clears the saved override, but a backend restart is required before tools return to the original launch directory.
Tool availability is not approval. Autopilot is selected per Chat request and is not stored as a global Settings policy; it cannot self-approve destructive or remote consequences.