[BUG] /feedback not working for bug reports
Resolved 💬 21 comments Opened Nov 3, 2025 by santoshmano Closed Mar 12, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The /feedback command does not work when invoked in Claude Code. When typing /feedback and pressing Enter, the command fails to execute or provide any response/interface for submitting feedback.
What Should Happen?
The /feedback command should:
Open a feedback submission interface, OR
Prompt the user to enter feedback text, OR
Provide a way to submit feedback directly to Anthropic
This command should allow users to quickly report issues, suggestions, or general feedback without leaving the CLI.
or disable or change the documentation around it, so that users know what to use /feedback for.
Error Messages/Logs
│ Submit Feedback / Bug Report │
│ │
│ Could not submit feedback. Please try again later. │
│ │
│ Press Enter to open your browser and draft a GitHub issue, or any other key to close.
Steps to Reproduce
- Clone a repo and /init it with claude.
- send feedback using /feedback.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.31
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
21 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
~~.A very minor bug/incomplete feature. Not a blocker really. ~~
Update: @genesiscz is right - losing feedback text is a pain.
Well it kinda is because I wrote a lengthy bug report and wanted to get drafted github issue in the browser and it disappeared even with the feedback text... well
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
I ran into this today too.
Same problem.
After an error with PDF analysis (https://github.com/anthropics/claude-code/issues/14038), it is impossible to send a bug report directly from the terminal.
still a problem in 2.1.7 on windows.
Given it's a built in way to report problems, which is capable of gathering useful context, it's really a shame it's been broken all this time. Feels like fixing it would save effort in the long run.
same issue on Mac in 2.1.19
same issue on ububtu with claude code version 2.1.19
Unknown skill: rate-limit-options
❯ /usage
⎿ Status dialog dismissed
getting /usage stats did not work just hangs so i decided to /bug that in which then results in this same error ;)
❯ /feedback
╭─────────────────────────────────────────────────────────
│ Submit Feedback / Bug Report │
│ │
│ Describe the issue below: │
│ │
│ /usage does not load my subscription stats the day after / when its been idle i guess for a long time so i need to spend some small tokens to check my tokens :) this is just a small nuance bug no biggy so FYI │
│ │
│ Could not submit feedback. Please try again later. │
│ │
│ Edit and press Enter to retry, or Esc to cancel │
│ │
╰─────────────────────────────────────────────────────────
Enter to continue · escape to cancel
Version: 2.1.12
the same
Suffering from the exact same issue. Would love to understand how I can debug or provide logs.
Me too
This has been broken for several months. I've never, ever been able to submit. It always just says "Could not submit feedback. Please try again later.", then it lets me futilely try again, then fails completely.
Same issue on macOS (Darwin 25.2.0), Claude Code v2.1.56, Anthropic API.
One additional UX issue: on the first attempt, the error is clear ("Could not submit feedback. Please try again later."). But when you retry, the command exits silently with no indication of whether the submission succeeded or failed (it says "Error submitting", but is that referring to the first attempt, or both?):
<img width="605" height="289" alt="First attempt - error message shown" src="https://github.com/user-attachments/assets/edf5d818-6f1b-4c54-ae1b-7f7ccdc998d1" />
<img width="509" height="151" alt="Retry - silent exit, unclear if it worked" src="https://github.com/user-attachments/assets/32305f13-fda4-4860-bc10-a41b669dda48" />
Even once the underlying submission bug is fixed, it would be good to always show a clear success/failure message so users aren't left guessing.
Also worth noting: this command is called
/feedbackin the CLI but/bugin the documentation, which makes it harder to find existing reports when searching. Filed #28565 to track the documentation gap.Additionally, the feedback submission failure doesn't get logged to the debug files (
~/.claude/debug/). Those files capture API calls, tool use, and hook events, but the/feedbacknetwork request and its error are not recorded. It would help if the error details were logged there so users can provide more useful bug reports when the submission fails.I ran into this today as well. I'm using claude-code version 2.1.58 on MacOS Tahoe 26.3.1.
At the very least it would be good to fix the "press enter to retry" part so that people don't lose the bug report they just finished typing in.
/feedback
⎿ Feedback / bug report submitted
works now for me :)
Still not working for me
<img width="1293" height="287" alt="Image" src="https://github.com/user-attachments/assets/ae05554b-0fdf-45da-baf6-7b833a3fab3c" />
<img width="716" height="196" alt="Image" src="https://github.com/user-attachments/assets/39c5d1fa-e6d2-4cc7-a6d0-fe818a1cefde" />
<img width="649" height="252" alt="Image" src="https://github.com/user-attachments/assets/4f047870-58ff-4193-b371-6276af7af459" />
FYI, I think the reason it didn't/doesn't work for me is probably because my company has disabled our github accounts from "contributing" outside of our own organization. I had to switch to my personal github account in order to add comments to existing bugs or create new ones.
That's not the problem, because I've always used a personal GitHub account
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.