Settings
What this solves
Settings configures you (profile, income, FIRE assumptions) and this instance (currency, appearance, developer and matching-engine preferences). A few sections are about how Lucius behaves or how your data is protected — this page links to their full guides instead of repeating them.
The sections
| Section | What it covers |
|---|---|
| Profile | About you, income & expenses, FIRE settings, notes for Lucius. Everything here feeds the model — an empty field is a gap in what Lucius knows, not a private setting. |
| Currency & format | Your base currency. On change, native-currency balances convert correctly, but a hand-typed amount in the old currency is simply re-read as the new one — the confirm dialog names what’s affected. |
| Appearance | Theme and display, instance-wide, commits as you change it — no separate Save. |
| AI | Provider/model running Lucius, memory, and spend. See Models & cost. |
| Permissions | What Lucius (or an automation) may do unasked. See Permissions. |
| Security | Instance security settings. See Security & privacy. |
| Data | Backups, restore, export, reset. See Backup & restore. |
| Developer | API token, connection snippets, MCP access for external clients. |
| Duplicate Detection | How aggressively matching flags duplicates, and pairs already ruled on — it won’t re-flag a decided pair. |
Things that trip people up
- Changing base currency doesn’t retroactively fix hand-typed amounts — read the confirm dialog first.
- Appearance changes apply instance-wide, not per-browser or per-person.
- Profile fields aren’t private — they’re context Lucius reads.