sudo robotctl configure

sudo robotctl configure
sudo robotctl configure --file ./bench-copy.toml

An interactive editor over /etc/robot/robotd.toml. Feature switches first, each key showing its current value against the default plus a line of documentation.

SPACE toggles, ENTER types a value, u reverts a key. Values in yellow (marked •) are where this robot diverges from the defaults — one glance tells you what has been changed on it.

Three properties worth trusting

It cannot disagree with the daemon. The schema, defaults and validation come from the same crate robotd parses the file with, and the key list is pinned complete by a test — a new [section] in the daemon shows up here or the build fails.

It cannot eat your file. Comments, ordering and keys from other releases survive untouched; only changed keys are written. Reverting a key removes it, along with its comment, rather than pinning the default — so the file stays a list of decisions, not a copy of the defaults.

It cannot write a file robotd refuses to start on. Every save is validated through the daemon’s own loader first, written atomically, and rejected with the reason.

The restart it offers

Daemons read the file once at startup, so saving offers a restart — of the ones that read what you changed: [media] is mediad, everything else is robotd.

The file is root-owned; without sudo the editor opens read-only. --file points it elsewhere for a bench copy.