claude-code - 💡(How to fix) Fix [Bug] Non-existent `/issue` command referenced in feedback survey prompt

Bug Description After responding to an in-session feedback survey prompt from Claude, I received this message:

▎ "Thanks for the feedback! Use /issue to report model behavior"

The /issue command does not exist. Typing it produces no output, no error, nothing.

This is not a minor UI typo. Consider the user journey:

1. Claude proactively asks me for feedback — I comply in good faith.
2. Claude then directs me to a non-existent command to report further issues.
3. A user who actually encounters problematic model behavior follows this instruction, gets silence, and reasonably assumes the report was submitted or the feature is broken on their end.

The net effect is that your own product actively misdirects users away from functional feedback channels. The working command is /feedback (alias /bug), but no user would discover that after being told to use /issue. This turns a feedback prompt into a dead end — the exact opposite of its stated purpose.

Whether this is negligence or oversight, the impact is the same: users who try to report model behavior problems are silently swallowed. For a company that publicly emphasizes safety and user feedback as a core part of its alignment strategy, shipping a broken feedback funnel is not a good look.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.143
• Feedback ID: ff7f26df-a888-4a91-b0b4-ca49122042ad

Errors

[{"error":"SyntaxError: JSON Parse error: Unrecognized token '/'\n    at <parse> (:0)\n    at parse (unknown)\n    at owq (/$bunfs/root/src/entrypoints/cli.js:182:10088)\n    at O (/$bunfs/root/src/entrypoints/cli.js:138:18426)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:184:1658)\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:19532:447)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-17T08:03:53.276Z"}]