Settings, privacy, and local data

Name change notice

Superconductor’s app name will be changing. During the transition, existing local paths and developer-facing names still use superconductor, including ~/.superconductor, .superconductor/config.json, the sc CLI, and SUPERCONDUCTOR_* environment variables.

Superconductor is local-first. Your repositories, prompts, credentials, terminal commands, and agent sessions stay on your Mac unless a configured agent CLI or native API-chat provider sends data to its model provider.

What Superconductor does not send

Superconductor does not send these to Superconductor servers:

• Hostnames.
• Usernames.
• Working directories.
• Project names.
• File paths.
• Branch names.
• Command inputs.
• Clipboard data.
• Code or prompts.

Agent CLIs and native API-chat providers may send prompts and code context to their configured model providers. That provider traffic is separate from Superconductor telemetry.

Anonymous telemetry

Superconductor sends anonymous usage telemetry to measure app usage and reliability. Each event carries a random install ID, random app session ID, app version, update channel, macOS version, and event timestamp. Session-ended events add duration and a clean-quit flag. Superconductor also emits a daily-active event on launch, window activation, or direct input.

Disable telemetry in:

Settings -> Privacy -> Share anonymous usage data

When you disable telemetry, Superconductor sends one final opt-out event, stops further sends, and deletes the local install ID and session-state file.

Local settings

Settings cover privacy, appearance, keybindings, providers, updates, repository behavior, and related workflow options. Appearance and layout settings include app theme mode, workspace color choices, sidebar visibility, auto-hide sidebars, panel widths, and font or scale controls.

For the user-facing workflow, see Layout, sidebars, and PiP.

Superconductor stores app settings in:

~/.superconductor/settings.json

The same directory also holds runtime files: the local database, hook wrappers for shells and agent CLIs, the local API socket, and caches.

Edit settings through the app. If you edit settings.json directly, quit Superconductor first. The app migrates old settings fields on startup.

Local data locations

Superconductor keeps state under ~/.superconductor/ and one folder per project. Quit the app before editing or deleting any of these files.

Path	Contents
~/.superconductor/settings.json	Global app and project settings.
~/.superconductor/db/superconductor.db	Local knowledge database (file index, history).
~/.superconductor/local-api.sock	Unix socket the sc CLI connects to.
~/.superconductor/local-api.json	Discovery file pointing at the live socket and PID.
~/.superconductor/hooks/	Wrapper scripts for shells and agent CLIs.
~/.superconductor/bin/sc	The sc CLI binary on PATH.
~/.superconductor/install_id	Random ID for anonymous telemetry. Removed when you opt out.
~/.superconductor/session_state.json	Telemetry session state. Removed when you opt out.
<project>/.superconductor/config.json	Repository-owned setup, run, and cleanup scripts.

Project settings

Superconductor stores project settings inside the main app settings file. They cover project defaults: branch naming, target branch, worktree location, setup and run scripts, cleanup hooks, provider defaults, and routing overrides.

Repository-owned setup lives in .superconductor/config.json at the project root. See Project config and scripts.

Credentials

Use your existing provider credentials and subscriptions. Superconductor does not replace provider authentication. If an agent CLI cannot authenticate in your regular terminal, fix that there before running it in Superconductor.