Guide·10 of 10
Settings
The window, the file, the shell, and every option.
01·The first minute
01link
Change anything
lode,The settings window carries every option the config holds and nothing else. Every row wears the config path it writes, so the window teaches the file as you use it.
Hold lode, then ,
02·When you are ready
02link
The file
~/.config/lodestar/lodestar.json holds only what differs from the defaults, so it reads as pure intent. It is watched: saving applies it the moment it parses, and a file that does not parse is announced once and left alone.
03Few know thislink
From the shell
lodestar config set writes one option. lodestar check validates everything, including profile names against the browsers on your machine. lodestar reload applies. lodestar schema prints every option, typed and described. lodestar diagnose is what to paste into an issue.
04link
A different lode key
Right ⌘ is the default. The trigger is one config line, and a non-ANSI keyboard can override key names under keys.
05link
Updates and login
The installed app checks daily, downloads in the background, verifies the signature, and applies quietly. It installs its own login agent so it survives reboots, and restarts itself after a crash but never after a clean quit.
03·The fine print
What nobody finds by pressing keys
- Every reload validates everything: syntax, unknown keys with a did-you-mean, types and ranges, and profile references against each browser's real profile list.
- The file's $schema line points at a schema written beside it, so an editor completes and documents every option as you type.
- State, the breaths and parked frames, is versioned and self-defending: every boot keeps a last known good copy.
- Logs are one line per event, greppable, rotating at five megabytes.
- The menu bar star holds the walk, updates, the issue reporter, the browser role, settings, the config, the log, and quit.
04·Why
Why it works this way
The window and the file cannot drift in either direction, because both are generated from one table in the source. Every writer, a hand edit, ⌘K, the coach, the shell, converges on the same canonical bytes. A configuration that can be read is one that can be trusted.
05·Settings
The settings behind this page
Read from the schema Lodestar itself emits. The settings window shows the same rows, and each wears the path it writes.
app.auto-updatebooleanKeep Lodestar current: check daily, verify the download, apply quietly when idle (installed app only).
$ lodestar config set app.auto-update trueapp.start-at-loginbooleanKeep the login LaunchAgent installed (installed app only).
$ lodestar config set app.start-at-login trueapp.show-menu-barbooleanShow the status item permanently; false hides it until lodestar is picked in the launcher.
$ lodestar config set app.show-menu-bar trueappearance.accentsystem · orangeThe colour of the cursor, lit letters, and the echoed query: the Mac's accent, or Lodestar's International Orange, set deeper in light mode so it stays readable.
$ lodestar config set appearance.accent …lode.triggerright-command · left-commandThe physical trigger for every gesture.
$ lodestar config set lode.trigger …keysobjectKeycode → key-name overrides for non-ANSI layouts.
$ lodestar config set keys …versionstringThe Lodestar release this config was written for.
$ lodestar config set version …