Diagnostics and logs
Daisy writes a quiet log file as it runs, so when something looks off — a slow finalize, a misbehaving mic, a provider call that didn't return — there's enough on disk to figure out what happened. Logs stay on your machine; nothing is shipped anywhere automatically.
Where the log lives
A single rotating log lives at logs/daisy.log inside your profile folder. The current day is in daisy.log; previous days roll into dated companions, and Daisy keeps the last 7 days. Older rotations are deleted on the next launch.
The file is plain text. You can open it in any editor.
Open the logs folder
Open Settings → Behavior and select Open logs folder. Daisy opens your file manager at the right path so you don't have to hunt for it.
Verbose debug logging
The default log is intentionally quiet — stage timings, errors, and the kind of context that helps pin down a real problem, without flooding the file with every backend init line.
If you're chasing something specific, toggle Verbose debug logging under Settings → Behavior. Daisy will log every model load, every provider call, and a lot more besides. Turn it back off when you're done so the file stays small.
When to share a log
If you reach out for help and we ask for a log:
- Reproduce the issue once with Verbose debug logging on.
- Open the logs folder.
- Send the relevant
daisy.log(or yesterday's rotation if it happened earlier in the week).
Scrub anything sensitive before sending — Daisy never includes audio or transcript text in the log by default, but custom titles or notes you typed during the session may appear in error context.
Good to know
- The console output you see if you launch Daisy from a terminal mirrors the log, minus a few framework lines.
- Logging is local-only. There's no "send diagnostics" button that ships anything in the background.