Add inline thumbs up/down feedback for responses
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
During a session, I often want to quickly signal whether a response was helpful or not — without interrupting my flow to type out why. A simple thumbs up / thumbs down on each response would let me do that.
- Typing "that was good" or "no, that's wrong" breaks flow during fast-paced work
- Quick feedback could help improve model responses over time (if collected)
- It mirrors what already exists in claude.ai's web interface — the CLI deserves parity here
Current workaround:
None really. I either say nothing or stop to type a correction, which is slower than it needs to be.
Proposed Solution
- A small 👍 / 👎 affordance on each response (maybe a keyboard shortcut)
- Optional — doesn't need to block or require explanation
- Bonus: option to add a quick note on thumbs down ("wrong approach", "missed context", etc.)
Alternative Solutions
None really. I either say nothing or stop to type a correction, which is slower than it needs to be.
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
I'm running a batch content transformation across 160+ WordPress posts. Claude makes a code change that touches two plugin files, updates error handling, adds a retry button, and bumps version numbers. The output is solid — everything I asked for. But I'm mid-workflow and about to zip up the plugins and deploy. I don't want to stop and type "looks good" — I just want to hit 👍 and keep moving.
Conversely, sometimes Claude makes a change I didn't ask for or misunderstands the scope. A quick 👎 would let me flag it instantly without composing a correction, and I could elaborate on my next message when I'm ready.
The point is: feedback should be as fast as the workflow. One keystroke, not one paragraph.
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗