What is in the Debug tab
Debug mode itself does not change how SpeakoFlow behaves. It does add an extra
“After 15 seconds” choice to the model-unload dropdowns in Settings →
Advanced, so reload timing is quick to test.
The —debug flag
Launch SpeakoFlow with--debug to raise logging to Trace for that run. It is never written to your saved settings, so the next launch returns to whatever log level is configured.
--debug does not reveal the Debug tab. Only the keyboard shortcut above does that.
From a terminal, you can also set RUST_LOG=trace to filter console output independently of the log level in Settings. See Command-line flags.
Where the log file is
The log file is namedspeakoflow and lives in your platform’s standard log directory, or in Data/logs in portable mode.
Rather than listing paths that vary by OS and install method, SpeakoFlow shows you the actual folder. Go to Settings → Privacy & data → Folders and click the button beside the log directory to open it in your file manager.
Logs rotate at 500 KB and one previous file is kept, so they stay small. A long session can push out earlier detail, so capture the log soon after reproducing a problem.
What release builds keep out of the log
The log level defaults to Debug and the file stays on disk, so the content matters. Release builds log only the length of transcripts, model replies, and search queries, never their text. In a development build, the full content is logged for debugging. This means a log file you attach to a bug report does not contain what you said. Settings contents (which include custom words, prompts, profiles, and memory notes) are also suppressed in release builds. API keys are never logged. TheSecretMap type behind every key field redacts its contents in all builds.