Settings page

Edit each routine's settings with cost notes, and the workspace's notifications, quiet hours and merge policy. What each save writes.

What it is

#/settings lists each producer’s settings from the definition, editable, with each one’s cost note, plus workspace options and facts about the Desk.

Why it exists

Settings are the safe way for people to change what a routine does without touching its prompt. The page shows the cost of each change before it is saved.

How it works

Producer settings

One form per producer, saved to settings/<producer> values. “Changes apply from the next run. Each run records the values it used.”

Type	Control	Checks
`toggle`	Switch	none
`number`	Number input	“Enter a number.”, plus `min` and `max`
`choice`	Select	“Choose one of the listed values.”
`list`	Items with “Add a value” and “Add, for example ”	An include list cannot be saved empty

Workspace

Saved to settings/workspace:

Notifications: Notify me: “Inbox only” or “Inbox plus push”.
Quiet hours: from and to. “No push between these times. Stored. No producer acts on this yet.”
Merge policy: per type, “Merge into one record” or “Keep separate per producer”.
Theme on this device: system, light or dark. “Kept in this browser only.”

“Saves from this page are last write wins: if two people change the same thing, the later save is kept.”

Desk template (“Created from template ” or “Created by routineos new”), definition version, RoutineOS version, and a document count (“The count covers shared documents. Each person’s read, done and seen marks are private and not counted here.”).

Since 0.5.0: every save writes settingsHistory/<id> {producer, before, after, at, by}, the last 50 are kept per producer, and each has Revert. Each list setting shows its own suggestions inline. The jobs-watch template gains excluded_title_words.

Worked example

The person raises lookback_days from 7 to 14 on Hiring Signals (“a longer window means more postings to compare”) and adds NZ to markets (“each market adds at least one job board search per run”). The next run’s settingsUsed records both.

Common pitfalls

Expecting push after choosing Inbox plus push. The preference is stored; no producer acts on it yet.
Two people editing at once. The later save wins.
Emptying an include list. It would match nothing, so it is refused.