Quickstart — first 30 minutes

1 · Install (one command)

curl -fsSL https://raw.githubusercontent.com/dxn111/sonderr/main/install.sh | sh

Requires Node.js 20+, npm and Git. The installer downloads the latest main source, installs under ~/.local/share/sonderr-v1.5 and links the sonderr command into ~/.local/bin. It never uses sudo, and reinstalling over an existing install preserves the old folder as a timestamped backup. Want to inspect first? Read install.sh — it's short and honest.

2 · Launch

sonderr

A local runtime starts and your browser opens http://127.0.0.1:4173. That browser tab is the product — the terminal command is only the launcher. If ~/.local/bin isn't on your PATH, add it as the installer instructs and open a new terminal.

3 · Chat with a free model — no API key

Pick Kilo Gateway in Settings → API & Models and choose a free-tagged model. No API key, no sign-up — anonymous use is rate-limited, and the free lineup can change. Add a Kilo API key later to unlock the full catalog, or run the local Sonderr-v1 model entirely offline (Models & providers →).

4 · Know the four modes

• Ask — read-only questions and research. Never changes files.
• Plan — scope work, inspect the workspace, build a task list.
• Build (default) — actual edits, patches and tools.
• Vision — image understanding: screenshots, charts, error photos, plus image generation/editing.

5 · Give it a real task

Attach a folder by starting Sonderr in it, then ask for something concrete: "map this repo and fix the failing test". Sonderr builds a workspace map, keeps a visible task list, patches files with exact diffs, runs project checks when you ask, and hands results back as artifact cards with copy/download (Workspace handbook →).

6 · Where your stuff lives

• ~/.sonderr — local settings, credentials (owner-only permissions), uploads, generated images, update log.
• ~/.local/share/sonderr-v1.5 — the application itself.
• Your workspace — your files, sandboxed. Tools can't reach outside it.

7 · Updates are required, not nagware

The managed install checks GitHub Releases at startup; a newer stable release blocks the workspace until installed — one click, with automatic rollback if anything fails (Why →). Only a normal HTTPS request goes to GitHub; nothing else about you leaves the machine.