Troubleshooting

"Windows protected your PC" / macOS "unidentified developer" or "damaged"

Expected — current builds aren't code-signed yet. Windows: More info → Run anyway. macOS: right-click the app → Open, or xattr -dr com.apple.quarantine /Applications/Veyandor.app. Signing/notarization is in progress.

The cockpit says "Veyandor is starting" / won't connect

Packaged builds start the bundled daemon automatically — give it a few seconds; it reconnects on its own. If you're running from source, start the daemon yourself with npm run daemon. If it persists, check that nothing else is holding the Veyandor pipe/socket and restart the app.

Claude Code "not detected" or "login not detected"

Veyandor needs your own Claude Code, logged in:

1. Install Claude Code (Anthropic's instructions).
2. Run claude, then /login.
3. Back in Veyandor, re-open onboarding via the top-bar Setup button and use Test connection.

Veyandor uses your subscription — you do not need an API key.

"not a git repo" when adding a project

Veyandor works on Git repositories so it can branch and merge agent work safely. git init the folder (or choose an existing repo) and add it again.

The "local" embedder isn't available

Packaged builds ship the keyword embedder only. Use keyword (the default), or run Veyandor from source to enable the local model (a one-time download).

"Check for updates" does nothing / errors

You're offline, or there's no newer release published. Updates are manual (Config → Updates) — Veyandor never checks in the background. On macOS, in-app updates don't apply until the app is notarized (pending).

Where is my data?

Everything lives under ~/.veyandor (the database, per-session git worktrees, and the local pipe/socket). Veyandor is local-first and doesn't upload your code or prompts.

Still stuck?

See Install and the Quickstart, or check the latest release notes at https://github.com/hockeyben/veyandor-releases/releases/latest.