What a bug report sends, and what it hides

In the Beta build, a bug report always carries your build code and nothing else unless you switch an extra on, and a live preview shows the exact text that will be sent with secrets and file paths already hidden.

Last checked against the app on · View as Markdown

Steps

  1. Open the report. Press the bug icon in the top bar, or press Ctrl+Shift+B. The shortcut works even while your cursor is in the message box. It does nothing while another dialog is open.
  2. Fill in "What happened?". It is the only required box. "What did you expect?" and "Steps to reproduce" are optional.
  3. Look under "What to include". The first row is "Build code", marked "Always sent". It says which build you are on: its code, version, edition and channel. Nothing about you or your machine. We cannot act on a report without it, so it cannot be turned off.
  4. Decide on the extras. Each one starts off. "System information" (your operating system, screen, theme, language, time zone, current page and app versions, with no paths or names). "Recent errors" (the last few error messages with time and code, no stack or file path). "The current conversation" (the last 12 messages of the open chat, which can quote your notes). "Update status". "Vault size" (counts only). "Chat model" (provider and model, never a key). "Contact me" (says we may contact you, sends no address). "Link to my account" (off by default on the Beta, and only available when you are signed in).
  5. Press "Show me" on a row to see the real, already-redacted data it would send.
  6. Know what is hidden. File paths, stack traces, anything shaped like a password or key, and computer names that are recognised. When something was hidden, the panel says "N spans were hidden before this was shown, and are marked [redacted: ...] below. What you see is what is sent." Check "Show me" for computer names, because they are hidden only when recognised.
  7. Read "Preview exactly what will be sent". It is live, and it is the very text that is sent.
  8. Press "Send bug report", or "Use the private inbox instead" for anything about your account or your notes. The inbox opens your mail client with the report on your clipboard to paste in.
  9. After a send the panel says "Filed. Thank you." and gives a Report ID or number to quote. "Copy ID" copies it.

How to tell it worked

The panel shows "Filed. Thank you." and a report number or ID.

If it does not work

You want your choices remembered next time.
They are. The conversation is the exception: it starts off every time. "Reset my choices" puts every extra back off. The same choices are in Settings, Connections and data, Privacy choices, under "What a bug report carries".
You want to know who can read it.
The panel says reports go to a private inbox that more than one person can read. Use the private inbox button for anything about your account or your notes.
You want to see the app’s own log.
Press "Open log folder" in the panel. It is a local record that stays on your machine and is not attached for you.
Sending failed.
See the guide on a bug report that did not send.