Discord feedback capture
Pick "Send to Usero" on any message and it lands in your inbox. Pick "Send to Usero and draft PR" and Usero also opens a GitHub pull request with a first pass at the fix. You review the diff and merge it. Nothing merges on its own.
Your community tells you what is broken before any tracker does. A bug dropped in #support, a feature begged for in #general, a screenshot in a DM. It gets a couple of reactions and scrolls away before anyone writes it down.
Discord is where a lot of product feedback now lives, and almost none of it survives the scroll. Someone posts "the export button does nothing on mobile" in a busy channel, three people react, and by the next message it is gone. The instinct is to copy the good ones into a tracker by hand, and nobody keeps that up past the first week. So the bar for a Discord feedback tool is not "can it save a message", a dozen bots do that and most want a privileged intent to read your whole server to do it. The real questions are how little work capture takes for the person who spotted the message, whether it pulls in your channels without permission, and what happens to the message after it is saved. Dropping it into yet another board is triage, not progress. The report is still a report and the fix is still unwritten.
How it works
Disclosure: I build Usero, so weigh that. You install the Usero Discord app on your server once, and from then on the whole surface is two context-menu commands. Right-click (or long-press on mobile) any message, open Apps, and pick one. "Send to Usero" captures that single message as a feedback item and stops. "Send to Usero and draft PR" captures it and, if your repo is connected, clones the repo, writes the change on a branch, and opens a GitHub pull request with a first pass at the fix. The capture is explicit every time, one message per action: there is no always-on bot, no webhook watching your channels, and Usero never requests the MESSAGE_CONTENT privileged intent. It reads a message only when a team member sends that exact one. The captured item carries the message text, the author display name, and the timestamp, tagged as discord in the same inbox as your widget, Slack, email, and app-review feedback, so it clusters with everything else. The PR body quotes the Discord message and links back to the feedback item, so when you merge you know which complaint you closed. You review the diff and merge it yourself. Usero never merges for you.
The only capture that survives a busy server is the one that takes a second. Right-click a message, open Apps, pick a command, done. No dashboard to open, no title to write, no copy-paste into a tracker. Anyone on the server who can open the context menu can capture, so feedback stops depending on whoever remembers to log it later.
This is the whole idea. "Send to Usero and draft PR" turns a complaint in a channel into a branch with the change already in it and a PR open on GitHub. For the class of fix that is a copy change, a missing validation, a wrong default, or a small component tweak, the work is done before you open the PR.
Usero never asks for the MESSAGE_CONTENT intent and never mirrors your channels. There is no always-on connection and no webhook reading messages in the background. Usero receives a message only when a team member explicitly sends that one through the Apps menu. Uninstall the app and new captures stop immediately, while the feedback already in your inbox stays.
A captured Discord message is feedback like any other in Usero, tagged with its source, the author display name, and the timestamp. It clusters alongside your widget, Slack, email, and app-store feedback, so ten people asking for the same thing across Discord and elsewhere collapse into one request you can answer with one PR.
The honest objection
No. Usero does not request the MESSAGE_CONTENT privileged intent and does not mirror your channels. It reads a message only when a team member right-clicks it and picks Send to Usero or Send to Usero and draft PR. There is no passive scraping and no always-on connection watching your server. The install asks for the minimum scopes to register the two context-menu commands, nothing more. If you uninstall the app, the commands stop and no further messages are captured.
FAQ
Right-click the message (long-press on mobile), open the Apps menu, and pick a command. "Send to Usero" captures it as a feedback item and stops. "Send to Usero and draft PR" captures it and, if a GitHub repo is connected, opens a pull request with a first pass at the fix. Capturing the same message twice does not create a duplicate.
No. It drafts a pull request and stops. Usero writes the change on a branch and opens the PR on GitHub. Your CI runs, your reviewers comment, and you merge it through your own branch protection. The merge is always your call.
No. Usero never requests the MESSAGE_CONTENT privileged intent and never mirrors your channels. The install requests only the minimum scopes to register the two context-menu commands. A message reaches Usero only when a team member explicitly sends that one through the Apps menu.
The message is still captured as feedback; Usero just skips the PR. Connect a repo in the GitHub section of the project and the command will draft PRs from then on. You can also open a PR later from the dashboard on a message you captured earlier.
Each one becomes a feedback item in your project inbox, tagged with discord as the source, carrying the message text, the author display name, and the capture timestamp. Discord does not expose message-author email, so that field is blank, same as Slack. The item clusters alongside your widget, Slack, email, and app-review feedback.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.