Privacy

Supacode is local-first. Your repositories, worktrees, terminal input and output, and agent conversations stay on your machine unless you intentionally use an external tool such as gh.

Stored locally

Supacode stores local state in places such as:

• ~/.supacode/settings.json
• managed worktrees under ~/.supacode/repos/<repository-name>/
• supacode.json files in repository roots if you create them
• local UI state such as pinned and archived worktrees, ordering, and last selection

Your repository contents and terminal transcripts are not uploaded by default.

Analytics

When enabled, Supacode sends anonymous product analytics to PostHog.

Examples of events currently emitted include:

• repository added or removed
• worktree created, deleted, pinned, and unpinned
• settings changed
• update checks
• run-script launches
• coarse action metadata such as the chosen open target

Analytics identify the device with a hardware UUID. The capture calls in the app do not send repository names, branch names, file contents, code, or terminal transcripts.

Crash reports

When enabled, Supacode starts Sentry for crash reporting and operational error logging.

For example, git failures log structured data such as the git operation name and exit code. Crash reporting can also include normal app crash information handled by Sentry.

GitHub integration

Supacode delegates GitHub operations to the gh CLI installed on your machine. Supacode does not store GitHub credentials itself. Authentication stays in gh.

Opting out

Settings (⌘,) lets you turn off:

• Share analytics with Supacode
• Share crash reports with Supacode
• GitHub integration

Analytics and crash-reporting changes require an app restart.

Third-party services

Supacode does not ship session replay, screen recording, or code-upload features.