Requirements

Sonderr needs three things on your machine: Node.js 20 or newer, npm, and Git. That is the whole list. Sonderr runs on Linux, macOS and other POSIX systems; Windows managed installs currently follow the release's manual upgrade instructions for updates. You do not need root access at any point — the installer never uses sudo.

Install in one command

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

What the installer actually does — nothing hidden:

• Downloads the latest main source from the public repository.
• Installs it under ~/.local/share/sonderr-v1.5 and installs dependencies from the lockfile.
• Links the sonderr command under ~/.local/bin.
• When reinstalling over a recognized Sonderr install, preserves the previous folder as a timestamped backup.

Want to inspect before you run? Read the install.sh source first. The installer tracks the latest main branch and is not a signed release package — reviewing it before running is a reasonable habit, and we say so on the box.

Start Sonderr

sonderr

The first launch starts the local runtime and opens your browser at http://127.0.0.1:4173. That browser tab is the product — sessions, task modes, artifacts and settings all live there. If ~/.local/bin is not on your PATH, the installer tells you the exact line to add; add it and open a new terminal.

Launch flags

Command	What it does
sonderr	Starts the local runtime and opens the browser automatically.
sonderr --no-open	Starts the runtime without opening a browser — you open the URL yourself.
sonderr --port 4300	Serves the workspace on a custom port instead of 4173.

If port 4173 is already busy, Sonderr automatically moves to the next available local port — you will see the actual URL in the terminal output.

Updates happen automatically

Managed installs check the official GitHub Releases endpoint when the workspace starts. When a newer stable release exists, the workspace blocks until you choose Install update & restart — Sonderr downloads the exact release tag, installs its locked dependencies, preserves the previous folder as a timestamped backup, and restarts on the same port and workspace. If any step fails, the updater restores and restarts the previous install. Diagnostics are written to ~/.sonderr/update.log with owner-only permissions. There is no "skip this version" option for managed releases; development checkouts are exempt.

Running from source

Developers can run a checkout directly instead of the managed install:

git clone https://github.com/dxn111/sonderr.git
cd sonderr
node bin/sonderr-1.5.js    # or: npm run start

Validate the launcher with npm run check. Source checkouts are exempt from the required-update gate — the updater never overwrites a development checkout or local changes.

Where files live

• ~/.local/share/sonderr-v1.5 — the application (managed installs).
• ~/.local/bin/sonderr — the launcher command.
• ~/.sonderr — runtime data: sessions, credentials (owner-only permissions), the optional Sonderr-v1 model files, update logs and uploads.