Problem
Users need an easy way to submit complaints and feedback from inside the desktop app instead of having to leave the product and manually file a GitHub issue.
The feedback flow should route reports into GitHub with the right existing repository labels. Do not invent new labels for this; use the labels already configured in the repo.
Scope
- Add clear feedback entry points throughout the app, especially settings/help surfaces, error states, failed task states, and places where users are likely to hit friction.
- Provide a lightweight form for complaints, bug reports, feature requests, and questions.
- Map form categories to existing GitHub labels such as
bug, enhancement, question, area:*, and appropriate priority:* labels where the app can infer severity.
- Include useful diagnostic context when the user consents, such as app version, platform, relevant session id, and selected log snippets.
- Make the submitted issue/comment readable and actionable for maintainers.
Acceptance criteria
- Users can submit feedback without manually opening GitHub and choosing labels themselves.
- The GitHub submission uses only labels that already exist in
browser-use/desktop.
- The form has complaint-oriented copy and does not make users decide implementation details.
- Sensitive data is excluded by default, and any diagnostic attachment/log inclusion requires clear user consent.
- There is test coverage for category-to-label mapping and the submission payload shape.
Problem
Users need an easy way to submit complaints and feedback from inside the desktop app instead of having to leave the product and manually file a GitHub issue.
The feedback flow should route reports into GitHub with the right existing repository labels. Do not invent new labels for this; use the labels already configured in the repo.
Scope
bug,enhancement,question,area:*, and appropriatepriority:*labels where the app can infer severity.Acceptance criteria
browser-use/desktop.