Logs

Where they live

One plain-text log file in your configured logs directory. It rotates at a few megabytes, keeping a small number of recent backups — it won’t consume your disk. Both the directory and file are readable only by the account running the app, same as your data directory.

What’s in it

Every request gets one line: how long it took, and how much of that was the database versus actual work — useful for telling a genuinely slow request from a database under load. Beyond that, ordinary operational events: what the app’s doing, what failed and why.

What’s deliberately kept out of it

AI-involving requests (attachments, images, documents Lucius reads) log about what happened — an id, a size, which model answered, how it was routed — never the actual content. Raw document text, an extracted image, or anything credential-shaped is never written, by design and checked for directly in the project’s own tests.

Reading it

Open the file directly, or ask Lucius — he can pull up the most recent entries without you leaving the conversation.

operations/performance — the per-request timing line this log carries
operations/security-and-privacy — the broader picture of what’s stored and locked down