Command reference Β· Cursor CLI
/feedback
Sends feedback directly to the Cursor team.
/feedback <message> sends a message directly to the Cursor team, without you leaving the CLI or opening a separate form. You append your text directly to the command β for example a bug description, a request for a missing feature, or an observation about the behavior of another command.
Because the command expects a text argument according to the docs (/feedback <message>), calling it without an attached message doesn't produce usable feedback β only the text turns it into meaningful feedback. The channel is meant for short, targeted notes that arise directly in the context of your current session, not for detailed bug reports with attachments or for requests where you need a timely personal reply. For that, the docs point to dedicated support channels.
π THE SAME TASK (βREPORT BUG/FEEDBACKβ) ON OTHER PLATFORMS
β WHEN TO USE IT?
Report a bug or missing feature
/feedback /rewind sometimes jumps back two turns instead of one
Give positive feedback about a workflow
/feedback The new plan mode helped me a lot with a big refactor
β WHEN NOT TO?
It's an urgent, individual support request
Feedback messages aren't designed for quick 1:1 support.
Better: Use Cursor's official support channel
Message is missing when calling the command
/feedback <message> requires a text argument according to the reference table β without an attached message the command doesn't produce usable feedback.
Better: Always attach a short text directly, e.g. /feedback <your observation>
SOURCES
- Cursor Docs β Slash Commands β cursor.com
MORE COMMANDS Β· Cursor CLI