Feedback & bug reports (desktop)
Something broken, confusing, or missing? Two paths from the desktop: the Feedback pill in the title bar, and the dashboard’s bug-report modal. Both show you exactly what they send.
Report from the title bar
Sending feedback from the titlebar pill
Click the Feedback pill
It is always visible in the title bar, in every mode — no menu digging while the problem is on screen.
Choose your screenshot
The flow asks first how to capture: App window, Whole screen, or No screenshot — your choice, every time. A Preview screenshot button shows exactly what the capture contains before anything is sent.
Describe what happened
Say what you expected and what happened instead, then keep or adjust the suggested title. One honest sentence beats a form full of fields.
Read the privacy disclosure
Before submitting, the flow states what the report includes. Nothing leaves your machine that you have not seen listed.
Submit
The report is filed as a GitHub issue you can follow to resolution. If filing fails — offline, no access — the flow falls back so the report is not lost: keep the text and file it manually.
Diagnostics in reports
Reports can include redacted diagnostics — basic app and environment details with sensitive values stripped before anything leaves your machine — so bugs arrive with the context needed to fix them. The wingman.feedback.includeDiagnostics setting controls this: turn it off to send reports with your words alone.
Report from the dashboard
Filing a bug from the dashboard
The dashboard has its own bug-report modal for problems in the dashboard pages themselves. Open it from the floating feedback button that rides along on every dashboard page, from the dashboard Settings page — or straight from the error screen when a page crashes. It follows the same shape: describe the problem, choose whether to attach a screenshot, and diagnostics are handled the same way.