What Lucius can do
Lucius is the assistant built into this app, not a chatbot bolted on the side. He reads the same ledger, accounts, budget, and portfolio data every screen reads, and changes something by calling the same functions the UI calls — no separate “AI view” that can drift from the real one.
What he’s actually good at
| Area | What he does |
|---|---|
| The ledger | Find, add, edit, categorize transactions; import a statement (CSV, OFX, QIF, CAMT, MT940, XLSX, or a PDF/photo); spot likely duplicates; explain a category call |
| Accounts and net worth | Create/reconcile accounts; “what’s my net worth” or “how has it moved,” any window |
| Budgeting | Assign and move money between envelopes, set targets, explain why one’s over or under |
| Investments | Positions, lots, cost basis, realized/unrealized gains across equities, crypto, commodities, property; record a buy, sell, vest, or option event |
| Payees and rules | Set a payee’s default category, write a categorization rule, apply either retroactively |
| Rich replies | A self-contained chart or report in the conversation; a structured financial report (net worth, income, spending, cash flow, budget vs. actual) for any period |
| Connectors, when configured | Sync a bank/brokerage connector, search the web, read (never send as) your email, reach an external tool over MCP — see Connectors |
| Memory and automations | Remember things about you across conversations (Memory); run the same work on a schedule (Automations) |
How he finds the right tool
He has hundreds of functions but you never need their names. A small set of the most-used ones stays ready by default; the rest he looks up by what you’re asking for, the way you’d search a help center. Describe what you want in plain language and he finds it, or asks first rather than guessing.
What he can’t do
- He can’t move money at another institution. No trade-placement or payment-sending path exists — Lucius can read a synced brokerage or bank connector but not submit an order or transfer through it. Trading on your behalf has to go through an external tool over MCP, and even then the call goes through the permission you set for it (see Permissions) — nothing here grants trading authority you can’t turn off.
- He can’t reach anything outside this one installation. No other account, no other user’s book, no cloud copy — everything lives in your own database on your own machine.
- Two bulk, model-chosen operations get an extra safety net. Deleting a filtered set of transactions and re-scanning your ledger for a payee rule are both “the model decides which rows” with no way to check the result if it chose wrong — on an ordinary Automation run, both still ask for approval regardless of any permission you’ve set. Exception: an Automation deliberately set to Skip all approvals means exactly that, these two included. See Automations.
- He can’t treat the deferred parts of the app as finished. Bank/brokerage connectors are real, working code with known open correctness gaps — see Bank & brokerage. Tax estimates, market intelligence, and equity-comp projections go further: real engines, real numbers, not yet held to this project’s bar for “trust these numbers.”
- He isn’t a guarantee of correctness. He reasons over what’s actually in your book. A mis-imported statement or a stale rate gets a confident answer from wrong data — fix the data, same as with any other assistant.