[FEATURE] Add config option to disable 'How is Claude doing?' feedback prompt
Status Closed — not planned
Maintainer reply None cached
Activity 6 comments · opened Apr 7, 2026 · closed Jun 3, 2026
Description
The "How is Claude doing this session?" feedback prompt keeps appearing when the terminal is idle. It cannot be easily dismissed and disrupts the workflow.
The irony: I was having a great session and would have rated "Good" — but the persistent, undismissable prompt is so annoying that now I want to rate "Bad". The feedback mechanism itself is creating negative feedback. 😄
Expected behavior
A config option like disableSessionFeedback: true to permanently disable the prompt.
Current behavior
- Prompt appears when idle
- Cannot be permanently dismissed
- No config option exists to disable it
claude config sethas no relevant setting
Related issues (all closed/locked)
- #19258 (6 👍)
- #10251
- #31305
- #8062
- #13366
This keeps getting reported and auto-closed. Please consider adding this as a setting.
Environment
- Claude Code v2.1.92
- macOS (Darwin 24.6.0)
- iTerm2
6 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is NOT a duplicate. All 3 referenced issues (#31305, #19258, #34284) are closed and locked — meaning no one can vote or comment on them.
This creates a loop: new issues get auto-closed as duplicates of old issues that are themselves closed and locked. The feature request never gets addressed.
Please either:
This has been requested since at least October 2025 with 6+ separate issues. A simple
disableSessionFeedbackconfig option is all we need.I asked Claude (Chat) about it and got these suggestions:
CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1~/.claude/settings.jsonto scope it speciically to Claude Code:CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1feedbackSurveyRateinsettings.json.Closing for now — inactive for too long. Please open a new issue if this is still relevant.
@fahrettinyilmaz will you make a new issue?
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.