When you would want it

"The AI stopped working" is hard to fix from a description. The log says which part failed, with the exact error, the version and the model you had selected, so a problem can be fixed from one report instead of a back-and-forth.

Where to find it

All Features → Report a problem with a debug log
Report a problem
Copy debug log
Save debug log

What you get out of it

Problems get fixed from one report: the log names the failing part, the exact error, the version and the model in use.
Assistant failures carry the provider's own error message, so a rate limit, a rejected key and a broken tool call are told apart immediately.
Nothing private goes with it: keys, prompts, answers, file contents, paths and project names are removed before anything is written.
Nothing is uploaded automatically - the log only leaves your machine when you send it.

How to use it, step by step

When something goes wrong, choose Help > Report a Problem. If the assistant failed, the error card's Report problem button opens the same form, already filled in.
Describe what you were doing and what happened.
Keep Include debug log ticked, and select See exactly what is included to read the text that will be attached.
Choose Send. The report goes with your message, the app version, your operating system and that log summary.
To share the whole log somewhere else - an e-mail, a chat, an issue - choose Help > Copy Debug Log and paste it, or Help > Save Debug Log to save it as a text file.

Why this beats the usual way

Most editors ask you to find a log folder, zip it and attach it, then hope nothing sensitive was inside. Agentfly's log is redacted as it is written, previewed before it is sent, and attached from the same Help menu you would open anyway.

Find it in Universal Search

Report a problem with a debug log · The workbench · bug report · report a bug · debug log · logs · diagnostics · send logs · support · something is broken · ai not working · error details · crash