saturday.ai

::docs :: getting started

your first session

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

Run saturn. You get an interactive prompt (»). Anything starting with / is a command; everything else is a turn for the agent.

» what's 15% of 2,340, and find me the latest news on local LLMs?
» read the file notes.md in my workspace and summarize it
» remember that I prefer concise answers

::what you see

  • –The plan rail — the drafted plan, then each step as it runs: the tool it calls, the observation that came back, and the judge's verdict. Every node is timed.
  • –The status bar — bottom-pinned: posture (only when it deviates from the safe default: ⚠ GATE OFF, a loosened tier, ⛓ AIRGAP), progress (▸node · iter · tools · elapsed · tok/s), context-fill meter, egress count, and CPU/RAM/GPU/VRAM.
  • –The answer — streamed token by token, with inline citations [n] and a Sources footer, low-confidence spans marked, and a one-line receipt: tokens, timing, and the trust segment (local-only, or exactly what left and how many calls faced the gate).
  • –The gate — when a step wants to write a file or run a command, the turn stops and shows you the exact diff or command. Bare Enter rejects.

::keys during a turn

keydoes
Esc (empty line)pause at the next step boundary and open the plan editor
type text, then Escsteer: the remaining plan is redrafted around your correction
Esc while the answer streamsfreeze the answer, edit it, and let the model continue from your prefix
Shift+Tabcycle the approval tier live (read_only → side_effecting → destructive)
Ctrl+Ccancel the turn (in an editor: abort)
Shift+Enter / Ctrl+Jinsert a newline in the prompt
Tabcomplete /commands and @paths

Type ahead while a turn runs — follow-ups queue and the queue depth shows in the status bar. Pastes of three or more lines collapse into a [paste #N] chip that re-expands at submit; Ctrl+E re-opens a chip for editing.

::first things to try

  1. 01/help — the grouped command list, opening with the trust-stack map (posture · activity · proof). Every command takes --help.
  2. 02/config setup — the health check: Ollama reachable, tier models pulled, capabilities declared.
  3. 03/tools — the registered tools and their risk tiers.
  4. 04/policy — the live gate posture as one object.
  5. 05/init — survey your workspace and draft SATURDAY.md, standing instructions loaded every turn.
  6. 06/trace — after a turn, the full drill-down of what just happened.

note

The workspace is database/workspace/ under your install (or SATURDAY_HOME). File tools are sandboxed to it. @path mentions in the prompt attach a file's contents to the turn, with tab completion.