Settings Reference

Tempest has two settings surfaces. Settings (the app-level panel) holds preferences that apply everywhere — appearance, terminal, git behavior, agent defaults. Project Settings (per project) holds the security and data configuration that applies when agents run inside that project.

App-level sections

The Settings panel has 13 sections, grouped as General plus a Help group. Section ids are as they appear in src/components/SettingsPanel.tsx.

Section id	Label	What it controls	Docs
`appearance`	Appearance	Theme picker, sidebar font size, and the default editor the toolbar Open-in button launches	Themes
`terminal`	Terminal	Terminal font size and family, cursor style, cursor blink, and scrollback	—
`git`	Git	Branch prefix for new worktree branches, and the commit message used when pushing agent changes	—
`intelligence`	Token Intelligence	Atlas code indexing (enable, auto-index new projects), semantic code search, and chat context compression	—
`security`	Security	Auto-approve agent tool calls, agent session isolation, precise agent status hooks, desktop notifications, anonymous telemetry	Security
`mobile`	Mobile (Beta)	Pairing a phone to drive Tempest remotely, via a QR code scanned from the Tempest mobile app	Mobile
`agents`	Agents	Per-agent launch defaults (extra flags, environment, working subdirectory), provider presets, custom agents, and the `claude` CLI path override	Agent manifest
`apikeys`	API Keys	Bring-your-own-key slots, stored in your OS credential manager	API Keys
`prompts`	Prompts	The saved Prompt Library, insertable into the message queue with one click	—
`keyboard`	Keybindings	Remappable keyboard shortcuts — click a binding to remap it	—
`attribution`	Attribution	Whether Tempest adds itself as a co-author on commits made inside your workspaces	—
`experimental`	Experimental	Opt-in features, currently the experimental Warp chat backend	—
`about`	About	App version, build info, and a developer-tools shortcut	—

App settings

Every field in AppSettings (src/store/appSettings.ts), with its type and default. Defaults live in SETTINGS_DEFAULTS in that file.

Where settings persist: app settings are one JSON blob in the SQLite app_state table under the key runtime, read and written through the db_load_app_state / db_set_app_state Tauri commands. See State.

The Appearance section’s theme picker covers the two built-in themes, tempest-dark and tempest-light — see Themes for what each contains and how to add your own.

Project Settings

Project Settings (ProjectSettingsPanel) are per project and configure what agents may do inside that project’s sessions. There are seven sections in three groups:

Group	Section	What it controls
Security	`sandbox`	Sandbox isolation mode (`off`, `monitor`, or `enforce`)
Security	`network`	Network policy (permissive or restrictive), with allow and block host lists
Security	`filesystem`	Read-write and read-only path mounts for the sandbox
Security	`permissions`	Whether sessions may skip permissions, and whether repo hooks may run
Security	`resources`	Per-session OS quotas: memory, processes, disk writes, CPU weight
Agent	`agent`	Which agents are permitted in this project
Data	`database`	Database isolation (branching) for the project’s sessions

Project Settings live per project: each project’s blob is stored as its own row in the same SQLite app_state table, keyed project-settings:{projectId}. When a repo contains a tempest.yml, its security config is clamped over the stored settings — the file may only tighten, never loosen — and that clamp is not persisted back into the row. See Security.

Getting Started

Workspaces

Agents

Chat & Threads

Tasks

Automations

Git

Terminal

Security & Isolation

Mobile

Configuration

Token Intelligence

Knowledge Base

Settings

Themes

Components

Internals

Contributing

Settings Reference

Settings Reference

App-level sections

App settings

Project Settings

​Settings Reference

​App-level sections

​App settings

​Project Settings

Settings Reference

App-level sections

App settings

Project Settings