sonder-config-and-flags

Catalogs every Sonder Runtime environment variable, config precedence rule, and consent gate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sonder Runtime exposes dozens of SONDER_* environment variables, TOML keys, and consent gates spread across two configuration layers, making it hard to know which knob controls what, what its default is, and where it is validated. This Skill provides a source-verified catalog so you can answer configuration questions and add new config options correctly. ## Core Features & Use Cases - Complete variable catalog: Every SONDER_* environment variable with its default, validation guard, and exact file:line source citation, organized by domain (paths, HTTP server, Ollama, consent gates, secrets, tuning, unsafe lab). - Two-layer config model: Explains the split between fail-closed startup config and the hot-reloadable runtime_policy.json, including precedence order from built-in defaults up to --set CLI overrides. - Config authoring checklist: An 8-step procedure for adding a new configuration axis, covering typed fields, env mapping, validation, export bridging, redaction, and tests. - Use Case: A user asks "how do I change the port" or "what does SONDER_ALLOW_CLOUD do" — the Skill returns the exact variable, default (11435), guard rules, and the source lines that enforce them. ## Quick Start Ask the assistant to explain what a specific SONDER_ environment variable does and what its default and validation rules are.

Frequently Asked Questions about sonder-config-and-flags

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

FAQPage Schema
How do I change the Sonder Runtime server port?

Set the SONDER_PORT environment variable or use --set server.port=12000 on the CLI; the default is 11435 and valid values range from 1 to 65535. You can inspect the merged result with python -m sonder_runtime config --json.

What is the configuration precedence order in Sonder Runtime?

Precedence runs from lowest to highest: built-in safe defaults, profile TOML, secrets env file, process environment, then --set CLI overrides. The config --json output lists which layers contributed each value.

Can secrets like API keys be stored in the sonder.toml file?

No, secrets are forbidden in TOML. Keys named api_key, auth_secret, backup_key, secret, or token in sonder.toml cause a validation error; secrets must come from the secrets env file or process environment.

What is the difference between startup config and runtime policy?

Startup config is a typed, fail-closed loader controlling network, filesystem, credentials, and consent gates, requiring a restart to change. Runtime policy is a hot-reloadable runtime_policy.json that can only adjust model aliases, lane routing, and NPU mode.

Why does setting SONDER_ALLOW_CLOUD not take effect at runtime?

Consent gates are startup-only booleans that default to false and cannot be changed through the hot-reloadable runtime policy, whose schema only covers models, routing, and NPU. You must set the variable and restart the server.

When should I not use this configuration skill?

Use sonder-run-and-operate for starting or stopping the server and running doctor, sonder-build-and-env for venv and pytest setup, and sonder-security-and-privacy for the threat-model rationale behind the consent gates.