Docs · Help

Troubleshooting & support

Most issues have a two-minute fix. Start here — if you still need a human, we are one email away.

Common issues

SymptomFix
sonderr: command not found~/.local/bin is not on your PATH. Add it as the installer instructed and open a new terminal.
Workspace on an unexpected portPort 4173 was busy — Sonderr automatically moved to the next free port. Check the terminal output for the actual URL, or force one with sonderr --port 4300.
Browser did not openStart with sonderr --no-open and open the printed URL manually, or just visit http://127.0.0.1:4173.
Workspace is locked with an update promptThat is the required-update gate. Choose Install update & restart. If it fails, the updater restores the previous install automatically — check ~/.sonderr/update.log for diagnostics and retry.
Update keeps failingRe-run the one-command installer; it preserves your previous folder as a timestamped backup and replaces the managed install. Your data under ~/.sonderr is untouched.
Sonderr-v1 not offeredThe local model needs Linux x64 with glibc 2.34+, GLIBCXX 3.4.31+, OpenSSL 3 and libgomp. Other platforms get the merged model with the CPU-only runtime instead.
Free model unavailable or rate-limitedAnonymous Kilo Gateway use is rate-limited and the free lineup can change. Add a Kilo API key for the broader catalog, or switch models in the picker.
File tool refuses a pathExpected: symlinks resolving outside the workspace and protected paths like .env or .sonderr are rejected by design. Move real work inside the workspace.
Project checks will not runChecks need Build mode, Full PC access in Settings → Tools & Access, and an explicit verification request in your current message.
Upload rejectedFiles are capped at 20 MB and stored per-session. Images route to Vision mode automatically.

Still stuck? Reach a human

Email support
FAST

Email lands straight with the team — usually answered within 24–48h, security issues the same day.

Community
GITHUB

Bugs and feature ideas go to the GitHub issues. For quick questions, email dxn1.0day@gmail.com.

Before you write: grab the diagnostics — ~/.sonderr/update.log for update issues, the terminal output for launch issues, and your Node version (node --version) for everything. It halves the back-and-forth.