Configuration

Settings and Storage

Global settings, local persistence, and the files Supacode writes on disk

Supacode stores its state locally.

Global settings sections

Supacode's settings window is organized into:

General
Notifications
Worktree
Updates
Advanced
GitHub
per-repository sections

Global settings file

Global settings live at:

~/.supacode/settings.json

The top-level file includes these keys:

global
repositories
repositoryRoots
pinnedWorktreeIDs

Worktree storage

Supacode creates managed worktrees under:

~/.supacode/repos/<repository-name>/

Each managed repository gets its own base directory so worktrees stay grouped and predictable.

Other persisted state

Supacode also persists local UI state such as:

archived worktree IDs
repository order
worktree order per repository
last focused worktree

This state is local to the app and used to restore your preferred organization.

Global settings you will probably touch first

appearance mode
default editor
notification behavior
prompted vs quick worktree creation
delete-local-branch behavior on worktree delete
update channel
analytics and crash reporting

Pull Requests and CI

Review PR status, inspect checks, and trigger common GitHub actions

Updates

Stable vs tip builds and how Supacode checks for new releases

On this page

Global settings sections Global settings file Worktree storage Other persisted state Global settings you will probably touch first Related docs