Settings

Settings is at the foot of the sidebar. Its tabs are You, Seats, Machines, Fleet rules and System.

You

Saved immediately, per user — nothing here touches the fleet. The conversation, notification, time-zone and date choices are kept in the record, so a second browser you sign in from starts with them; the look, the mode and the language are kept in this browser.

• Look — theme (system, light, dark), text size, density, and the console mode (Simple or Advanced).
• Interaction language — English or Polish. The record keeps its own language.
• Conversations — whether a turn's cost shows on hover, always or never; whether tool lines are folded or open; whether Enter or Cmd-Enter sends; whether opening a role shows its last conversation or a new one; short completions on Tab.
• Tell me about — which kinds of event appear in Today.
• Signing — every owner act asks for your passkey; this is stated, not a choice.
• Profile — your time zone and date format.
• Closing the console — conversations keep running on the server after the last tab closes; this decides whether they keep running, close, or you are asked.

The identity card is read-only: your display name, the operator identifier acts are signed with, the configuration version that signed you in, and this device's key fingerprint. Changing any of them is a registry act, not a console setting. The This device card is where you sign out.

Seats and Machines

Seats lists the seats on record — an account on a machine; a seat allows a set of roles — and holds Cast roles, where you pick the seat each of Advisor, Master and Scribe works from. Changing a seat there does not end a conversation that is already running. Machines lists the machines your seats run on. A machine is admitted when Saphan Studio is installed on it; a remote one is admitted from the command line — see Machines and seats.

Fleet rules and System

⚠ Neither changes anything in this release. Fleet rules (how the fleet chooses models, rounds and reviews, and how it writes to git) is sample data throughout. System shows the workspace facts the console can read, and its controls — record language, event retention, routing, caps, budget alarms, default review, who may sign decisions — are sample data, marked as such. A change on either tab is refused with "Sample data — this act is not wired yet", and nothing is sent.

The workspace-level settings are read from the configuration file, and changing them is an operator's act on the host — see Configuration.