Operational setup lives in one settings surface.
Polystro’s settings are not an afterthought. They expose the practical configuration needed for a real multi-agent desktop workflow: detected CLIs, API keys, MCP, skills, custom commands, keybindings, notifications, voice, remote devices, and editor behavior.
Settings Surface
Settings are organized into tabs for general behavior, appearance, agents, remote devices, editor preferences, scripts, automations, slash commands, skills, voice, MCP, keybindings, and notifications.
That matters because the desktop app is doing real operational work on your machine. The settings surface exists to make those moving parts legible instead of burying them in config files.
General and Runtime
The general tab controls how the desktop behaves during real work: auto save, format on save, auto-commit on completion, turn-history retention, commit-message generation, agent worktree storage, and whether multiple agents may touch the same worktree at once.
Editing defaults
Auto-save and format-on-save affect how quickly the local repo reflects what you and the agents are doing.
Undo and commit behavior
Turn-history retention and auto-commit settings change how easy it is to step backward after a completed run.
Worktree storage
You can choose where isolated agent worktrees live and reset that directory later if needed.
Concurrency policy
Concurrent worktree access is an explicit power-user toggle because it increases file-conflict risk.
Appearance, Browser, and Layout
Appearance settings go beyond theme. Polystro also exposes chat collapse defaults, per-CLI session visibility limits, terminal font size and family, browser tab position, browser tab visibility, max active browser tabs, and layout or zone placement controls where that rollout is enabled.
Why these controls matter
CLI and API Setup
Polystro detects supported agent CLIs, reports version and health status, lets you choose defaults, and supports API key overrides when the right environment variables are not already available through your shell.
Detected CLIs
Supported CLIs are surfaced with availability, auth status, and diagnostics.
Default behavior
You can choose defaults like commit-message generation and per-CLI behavior from Settings.
Environment overrides
API keys can be overridden from the app when shell-level configuration is not enough.
Worktree control
Settings also expose where agent workspaces live and whether concurrent worktree access is allowed.
Skills and MCP
Skills and MCP server configuration are first-class settings because they shape what your connected CLIs can do. Polystro can store skill definitions, sync them toward installed CLIs, and manage MCP server definitions in one place.
Why this belongs in Polystro
Voice, Notifications, and Remote Devices
Voice settings cover microphone permissions, device selection, language, and shortcut capture. Notification settings control which events should interrupt you and whether they should only appear when the desktop window is unfocused.
The same area also exposes trusted remote devices for the local viewer, so you can revoke previously paired devices without leaving the app.
Keybindings and Editor
Keybindings are configurable with conflict detection, while the editor tab lets you choose the external editor Polystro should use when a file needs to be opened outside the in-app surfaces.
Together, these settings let the desktop shell adapt to an existing workflow instead of forcing a fixed interaction style.
Configure CLI detection and auth
Go deeper on supported CLIs, provider auth expectations, API key overrides, and session defaults.
Learn fast navigation
See how command-palette search, session shortcuts, and custom keybindings fit together.
Configure command routing
See how custom commands, model routing, and routing policies live inside Settings.
Review support and account flows
Learn where updates, bug reports, device limits, and license recovery are handled.