We send anonymous, allow‑listed events (app start/close, feature usage names, app/platform versions) to PostHog.
We do not send code, file paths, repo names, prompts, or PII.

Disable telemetry:

• In the app: Settings → General → Privacy & Telemetry (toggle off)
• Or via env var before launch:

TELEMETRY_ENABLED=false

Full details: see docs/telemetry.md.

App data is local‑first. We store app state in a local SQLite database:

macOS:   ~/Library/Application Support/emdash/emdash.db
Windows: %APPDATA%\emdash\emdash.db
Linux:   ~/.config/emdash/emdash.db

Privacy Note: While Emdash itself stores data locally, when you use any coding agent (Claude Code, Codex, Qwen, etc.), your code and prompts are sent to that provider's cloud API servers for processing. Each provider has their own data handling and retention policies.

You can reset the local DB by deleting it (quit the app first). The file is recreated on next launch.

Only if you want GitHub features (open PRs from Emdash, fetch repo info, GitHub Issues integration).
Install & sign in:

gh auth login

If you don’t use GitHub features, you can skip installing gh.

Emdash is provider‑agnostic and built to add CLIs quickly.

• Open a PR following the Contributing Guide (CONTRIBUTING.md).
• Include: provider name, how it’s invoked (CLI command), auth notes, and minimal setup steps.
• We’ll add it to the Integrations matrix and wire up provider selection in the UI.

If you’re unsure where to start, open an issue with the CLI’s link and typical commands.

This usually happens after switching Node/Electron versions.

1. Rebuild native modules:

npm run rebuild

2. If that fails, clean and reinstall:

npm run reset

(Resets node_modules, reinstalls, and re‑builds Electron native deps.)

• Filesystem/Git: to read/write your repo and create Git worktrees for isolation.
• Network: only for provider CLIs you choose to use (e.g., Codex, Claude) and optional GitHub actions.
• Local DB: to store your app state in SQLite on your machine.

Emdash itself does not send your code or chats to any servers. Third‑party CLIs may transmit data per their policies.

Yes! Emdash supports remote development via SSH.

Setup:

1. Go to Settings → SSH Connections and add your server details
2. Choose authentication: SSH agent (recommended), private key, or password
3. Add a remote project and specify the path on the server

Requirements:

• SSH access to the remote server
• Git installed on the remote server
• For agent auth: SSH agent running with your key loaded (ssh-add -l)

See docs/ssh-setup.md for detailed setup instructions and docs/ssh-architecture.md for technical details.