docs.

introduction

What Saturn is, the two guarantees it is built around, and how a turn flows through the engine.

installation

The one-line installer, pipx/uv, and manual installs from source — plus the environment knobs each one honors.

your first session

The prompt, the plan rail, the status bar, and the keys that matter during a turn.

plans & steering

The plan rail is the control surface: review and edit the plan, steer a running turn, write your own plan with /draft, and what a removed step really removes.

the approval gate

Risk tiers, the y/N/s/a/e prompt, what a grant covers and how long it lives, shell prefix allowlists, and /policy — the one front door for every relaxation.

the trust stack

The egress ledger and air gap, prompt-injection quarantine, the per-answer trust receipt, secret handling, and why every loosened posture is session-only unless saved.

answers you can check

Citations and sources, token-confidence marking, the groundedness check on every figure, and interrupt-and-correct.

tools

Every built-in tool, its risk tier, and what it actually does — files, shell, web, calculator, clock, knowledge base, memory, and ask_user.

mcp servers

Connect any Model Context Protocol server from config.yaml — its tools face the same gate as everything else and never self-declare their risk.

documents, memory & workspace

The local knowledge base (RAG), durable memory, per-workspace instructions in SATURDAY.md, @file mentions, and /undo.

observability & replay

/trace: the drill-down of any recorded run, why it decided what it did, what the model was actually sent, exports, and offline replay.

headless & the cli

saturn -p and -q for scripts and pipes, --json, --export, --yolo, --replay — and the deny-by-default gate when no human is present.

slash commands

The complete command list. Every command takes --help.

configuration & models

config.yaml: hardware tiers and model roles, runtime and safety knobs, web/RAG/MCP/shell sections — and which settings persist.