sonder-run-and-operate

Operate the Sonder runtime lifecycle including serve, drain, backup, restore, and updates.

6|3|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Krilliac/Sonder-runtime --skill sonder-run-and-operate-krilliac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sonder-run-and-operate
Source: https://github.com/Krilliac/Sonder-runtime/tree/main/.claude/skills/sonder-run-and-operate
Command: npx skills add https://github.com/Krilliac/Sonder-runtime --skill sonder-run-and-operate-krilliac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a local-first AI runtime day to day involves many moving parts: starting the Ollama-backed API server, draining it safely, managing PID files and logs, taking backups, and applying signed updates. This Skill provides a copy-pasteable operational runbook so you never have to guess which subcommand, port, or state path applies. ## Core Features & Use Cases - Lifecycle Management: Start, stop, restart, and gracefully drain the Sonder API server (port 11435), the Ollama daemon (11434), and the mobile-control launcher (11436) via python -m sonder_runtime subcommands, Windows/POSIX launchers, or the headless supervisor. - Backup, Restore, and Updates: Create, verify, prune, and apply backups; install signature-verified update bundles with rollback; or run guarded fast-forward updates on source checkouts. - State and Deployment Knowledge: Know exactly where databases, logs, and PID files land per OS, and deploy as a loopback-only systemd service on Linux. - Use Case: You need to restart a production Sonder server after a schema migration. The Skill tells you to run migrate --adopt-epoch2, then serve, and how to verify with a smoke test against /v1/chat/completions. ## Quick Start Ask the assistant to start the Sonder API server and verify it is responding with a smoke test.

Frequently Asked Questions about sonder-run-and-operate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start the Sonder runtime API server?

Run python -m sonder_runtime serve from the repo root using the venv Python, which binds port 11435 after fail-closed preflight checks. On Windows you can also use sonder-serve.cmd, or sonder_headless.py start for console-free operation.

How do I back up and restore Sonder runtime state?

Use python -m sonder_runtime backup create to write a backup to the state-home backups directory, then backup verify to check integrity. Restore with restore verify, restore smoke, and finally restore apply <path> <destination> --confirm restore.

Why does sonder serve refuse to bind with a migration error?

Serve exits if the state store has not adopted schema epoch 2, printing a migration-required message. Fix it by running python -m sonder_runtime migrate --adopt-epoch2, then start serve again.

Where does Sonder store logs, PID files, and databases?

State lives under a per-OS state home: %LOCALAPPDATA%\sonder on Windows, ~/Library/Application Support/sonder on macOS, and ~/.local/share/sonder on Linux. PID files and logs sit in the run/ subdirectory, with databases like memory.db at the root.

Can I expose the Sonder API port 11435 to the network?

No, the deployment path is loopback-only by design and you should never port-forward 11435. For remote clients, use the server-private profile with a TLS reverse proxy as described in the secure-remote-access runbook.

When should I not use this run-and-operate skill?

Do not use it for creating the venv or installing dependencies, which belongs to sonder-build-and-env. Interpreting doctor or preflight output belongs to sonder-diagnostics-and-tooling, and full config reference belongs to sonder-config-and-flags.