claude-code - 💡(How to fix) Fix Add setting to disable in-session satisfaction survey [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48643Fetched 2026-04-16 06:54:52
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Request

Add a settings.json option (e.g., disableFeedbackSurvey: true) to suppress the periodic "How am I doing?" satisfaction survey that appears during sessions.

Motivation

During long, high-throughput interactive sessions (e.g., article review workflows with 40+ back-and-forth exchanges), the survey interrupts flow. The numbered response (1-5) can also be misinterpreted as input to the current task.

Power users who are satisfied and actively using Claude Code daily don't need periodic prompting. If they have feedback, they'll provide it proactively or via GitHub issues.

Suggested implementation

Either:

  • A settings.json key: "disableFeedbackSurvey": true
  • Or an env var: CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1

Thank you!

extent analysis

TL;DR

Adding a disableFeedbackSurvey option to settings.json or setting the CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY environment variable to 1 may suppress the periodic satisfaction survey.

Guidance

  • Review the current implementation of the satisfaction survey to determine how it is triggered and how user feedback is collected.
  • Consider adding a disableFeedbackSurvey key to the settings.json file or supporting the CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY environment variable to provide a configurable option for users.
  • Evaluate the potential impact of disabling the survey on user engagement and feedback collection, and consider alternative methods for collecting user feedback.
  • Test the proposed solution to ensure it effectively suppresses the survey without introducing unintended side effects.

Example

{
  "disableFeedbackSurvey": true
}

or

export CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1

Notes

The proposed solution assumes that the satisfaction survey is implemented in a way that can be easily disabled via a configuration option or environment variable. Additional testing and evaluation may be necessary to ensure the solution meets the requirements and does not introduce unintended consequences.

Recommendation

Apply workaround: Add a disableFeedbackSurvey option to settings.json or set the CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY environment variable to 1, as this provides a configurable solution for users to suppress the survey.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING