Skip to main content

Diagnostics and logs

Use logging and diagnostics when something fails silently — hotkeys, config, or crashes. Controls live under Settings → Advanced. Beta builds also upload sanitized diagnostic bundles automatically (90-day retention). Stable builds only send telemetry if you opt in under Privacy.

Enable and download logs

  1. Open Settings → Advanced → Logging.
  2. Turn Enable Logging on (pre-release/dev builds may already force debug logging).
  3. Set Log Level (Error → Debug) and Max Records if you need a longer buffer.
  4. Reproduce the problem once.
  5. Click Download log or Download CSV, and optionally Open Data Folder.
  6. Attach the file to a GitHub issue or support email with OS and version from Settings → About.
What to share

Share downloaded logs and a short repro. Do not paste API keys. Prefer the export buttons over copying raw folders unless support asks.

Built-in diagnostics

Under Settings → Advanced → Diagnostics you can:

  1. Review environment info (OS, app version).
  2. Run hotkey hook / key-capture / matching tests.
  3. Analyze config health.
  4. Run a system health check.
  5. Save diagnostic report — structured results plus a log excerpt for support.

Logging may rise to Debug only while a test runs.

Beta diagnostic uploads

TopicDetail
WhenPre-release (beta) builds
WhatSanitized diagnostic log bundles (warnings, errors, debug-oriented bundles — not raw audio or full transcripts as product telemetry)
Opt-outNone on beta — disclosed under Settings → Privacy
Retention90 days (with per-user/device and daily upload caps)
StableNo forced log upload; telemetry is consent-gated

Channel choice: Updating and the beta channel. Privacy toggles: Privacy settings.

Sanitization is not anonymity theater

Bundles are scrubbed of obvious secrets where possible, but treat exports as sensitive. Only send them to official support channels.