Diagnostics
Echo's Settings navigation exposes Events & Logs and About under Diagnostics. Soundwave is also present for developer/admin mode and is not part of the normal support path.
Events and log journal
The Events & Logs panel keeps both records behind one tabbed view: Events (the app's own event journal), Log Journal (the log files under ~/.budgie/echo/logs), and an All view across both. A notification-threshold select decides which events also raise a toast — Debug, Info, Warning, or Error, with Error as the default. The toolbar above the list provides a level filter, a text search, a log-file picker, auto-refresh, and Clear actions per tab.
Events is the first place to inspect after a failed recording, model operation, provider request, or workflow run. Rows expand to show the structured detail they carry. Clearing Events does not clear the log files. Event details can include model names, action details, identifiers, or errors, so inspect them before copying.
Clear Logs permanently deletes the log files after confirmation.
Logs can contain paths, endpoint information, account context, action input, or other values produced during a failure. Do not assume a log is safe merely because it is diagnostic output.
About
About shows the app version, account and plan state, cloud and local quota, the onboarding reset, and the support form; see About. Direct-distribution builds provide the in-app update check; Mac App Store builds receive updates through the store.
Report a Bug sends a title and description through the authenticated gateway. If Include application logs is selected, Echo attaches up to the most recent 500 lines, capped at about 100 KB, from the latest Echo log. The request can also include account identifiers, app version, and platform. Uncheck the option when the log cannot be reviewed and safely shared.
Troubleshooting bundle
For a useful report, collect:
- Echo version, platform, and distribution channel from About and Platform Support.
- The exact trigger or button used and the smallest reproducible workflow.
- The first relevant Warning or Error in Events.
- A short, relevant section of Logs, if needed.
- Expected result, actual result, and whether retrying changed the outcome.
Avoid attaching an entire log history when a small excerpt identifies the failure.
Safe redaction
Before submitting or pasting diagnostics, remove:
- transcription text, selected text, prompts, workflow outputs, and customer data;
- home-directory, file, recording, and private network paths;
- access tokens, API keys, cookies, authorization headers, and deep-link values;
- email addresses, account IDs, recipe IDs, machine identifiers, and endpoint URLs when not essential;
- unrelated lines before and after the failure.
Redaction is your final check: Events and Logs are operational records, not a privacy boundary. Preserve the timestamp, severity, subsystem, app version, and error text needed to diagnose the issue.
Continue with Troubleshooting for issue-specific recovery steps.