Operations

Operations is millfolio's engine room — the single place to see what the machine is doing. Most of the time you can ignore it; it's here when you want to watch a run finish, tune how hard the background work pushes, or find a file on disk.

One queue, one job at a time

millfolio does two kinds of heavy background work: indexing your documents and AI-tagging your transactions. Both lean on the same on-device model, so millfolio runs them through one queue, one job at a time — they never compete for the engine, and your Mac never has two runs fighting over it.

Two things follow from that, and they're the whole point:

• Your questions always come first. Ask something while a folder is indexing and your question jumps the line — it runs immediately, and the background work resumes right after. Asking is never stuck behind a long run.
• Nothing stays wedged. If a background run gets interrupted — say you quit the app mid-index — millfolio cleans it up automatically on the next launch. There's no stuck job to clear and no wedged queue to reset.

Operations lays this out top to bottom, from what's happening this second down to the details.

Now

The top of the view is the job running right now — either an Index run or an AI-tag Backfill — with its elapsed time and a progress read-out. Below it is the queue behind it: how many files are waiting ("N files queued") and the next items in line. When nothing is running, it simply says so.

Controls

Two controls govern all the background work — both indexing and backfill:

• Pause for 1 hr. Stops the background engine for an hour — handy if you want your Mac's full attention elsewhere. While paused you get a countdown and a Resume button to end it early. (Your questions still work while paused — only the background runs are held.)
• Priority. How aggressively the background work runs — high, medium, or low. Lower priority chips away more gently and leaves more headroom for everything else; higher priority drains the queue faster. This setting now applies to indexing as well as backfill.

History

A log of past operations — index, re-index, and backfill runs — newest first, each with its duration and outcome. Failed runs are surfaced here: a run that crashed shows ✗ failed with the reason, so you're never left guessing why a folder didn't finish. It's the answer to "did that big re-index actually complete?"

System

A live read-out of the machine: GPU, memory, and disk usage, and the active model answering your questions. Alongside it is where millfolio keeps things on disk — your vault data and the log files — so you can inspect or clean up. Everything lives under millfolio's own folder, ~/Library/Application Support/Millfolio, which is what makes it clean to remove: the engine, the toolchain, and the model weights all sit in one place.

The logs are also where a per-ask transcript lives — the program a question generated and what it computed. If an answer ever looks wrong, that's where to look to see exactly how millfolio arrived at it.

Backfill

At the bottom is the AI-tag backfill detail: a per-tag progress bar for each AI tag, plus a Backfill now button that drains the queue immediately so you can watch it complete. AI tags classify each transaction with the on-device model, and because that runs in the background, asking is never blocked on it. See Tag backfill for the full picture of how the ledger keeps re-runs cheap.

Status bar

A slim status bar sits in the bottom-left corner of the app, visible on every tab — a quick glance at what's running without opening Operations:

• Model — the on-device model currently answering your questions.
• GPU avg — average GPU utilization, so you can see the engine working.
• MEM used % — how much of your system memory is in use.
• Build — the millfolio version you're running.
• Backfill — a chip showing AI-tag backfill progress; it clears when everything is tagged.

Looking for performance numbers — how fast questions run on your Mac? Those moved to their own tab: see Stats.