Settings Overview

How settings are organised, the two scopes they apply at, and where each group of options lives.

Opening Settings

• Press Cmd+, / Ctrl+,
• Click the Settings gear in the dock, available on every view
• Click the gear on a project's overview page to land on that project's own settings
• Use the Command Palette (Cmd+K) and select "Open Settings"

Cmd+W closes the settings panel rather than the window.

The categories

The sidebar groups thirteen categories into four blocks. Search at the top of the sidebar finds any individual setting by name and jumps to it.

Model connections, voice, embeddings and image generation all live under Models. Apps and MCP servers are not in settings at all: they have their own Apps and Integrations pages in the sidebar.

Global and per-project

Most settings are global. A project's own settings page carries the ones that only make sense per repository, and those always win over the global default:

• Project Name and Color shown in the sidebar
• App Root for monorepos where the app is not at the project root
• Dev Command, Port and Auto-start for the dev server
• Permissions: inherit the global setting, auto-approve everything, or ask every time
• Execution Environment: inherit, or a custom sandbox policy for this project
• Python Environment: a detected virtual environment or a custom activation command, optionally enforced on every Bash command (see Python Environments)
• The profile this project activates, and which apps and MCP servers it may use