Desktop (Linux): /feedback stuck in background session, sent as text; queued feedback drafts never shown
Status Open
Reported on v2.1.295
Maintainer reply None cached
Activity 0 comments · opened Oct 9, 2026
Environment: Claude Code 2.1.295, Claude Desktop app (Linux beta), Linux Mint 22 Xfce, background (remote) Code session. Model: Opus 5.5.
1. /feedback doesn't work in a desktop-app background session, and its suggestion box gets stuck
- Typing
/in the Code tab shows the suggestion "feedback — Send feedback, report a bug, or share your session". - Picking it doesn't open the feedback form. The literal text
/feedbackis sent to the model as a chat message. - After that, the "feedback" suggestion stays on screen above the empty message box. Esc doesn't close it, and Ctrl+R (window reload) doesn't either.
- Each time the user presses Enter,
/feedbackis added to their message, so their messages arrive with/feedbackscattered through them. - Voice input stopped working during the same period (may or may not be related).
2. Feedback drafts queued by the model never reach /feedback
- The model's feedback-draft tool says: "queued locally… the user can review and send it with /feedback".
/feedbackshows nothing to review. Six drafts collected over two weeks (CLI 2.1.283 → 2.1.295) in~/.claude/feedback/drafts/with"status": "queued"and were never sent.- Result: the model told the user to approve a report that could never be approved.
3. Model behavior (context for the drafts above)
- The user had built mods (plugin hooks) to trim the 400+ account-synced plugin skills loaded in every session. One mod silently did nothing because a catalog file it depends on was missing.
- Instead of checking the user's mods first, the model asked a needless multiple-choice question, then tried to re-run the mod's logic by hand.
Expected: /feedback either works in background sessions or isn't offered there; the suggestion box can be closed; queued feedback drafts are shown in /feedback or not promised.
🤖 Generated with Claude Code