Hey HN, Boris from the Claude Code team here. Sharing a bit about why we have this survey, how we use it, and how to opt out of it-
1. We use session quality feedback as a signal to make sure Claude Code users are having a good time. It's helpful data for us to more quickly spot & prevent incidents like https://www.anthropic.com/engineering/a-postmortem-of-three-.... There was a bug where we were showing the survey too often, which is now fixed (it was annoying and a misconfiguration on our part).
2. Giving session quality feedback is totally optional. When you provide feedback, we just collect your numerical rating and some metadata (like OS, terminal, etc.). Giving feedback doesn't cause us to log your conversation, code, or anything like that. (docs: https://code.claude.com/docs/en/data-usage#session-quality-s...)
3. We don't train on quality feedback data. This is documented in the link above.
4. If you don't want to give feedback, you can permanently turn it off for yourself by setting CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1 in your env or settings.json file. (docs: https://code.claude.com/docs/en/settings)
5. To permanently turn off the feedback survey for your whole company, set CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1 in the settings.json checked into your codebase, or in your enterprise-managed settings.json (docs: https://code.claude.com/docs/en/settings)
6. You can also opt out of both telemetry + survey by setting CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1, or you can more granularly opt out with DISABLE_ERROR_REPORTING=1, DISABLE_TELEMETRY=1, etc. (also documented in the settings docs)
Security and privacy are very important, and we spend a lot of time getting these right. You have full control over data usage, telemetry, and training, and these are configurable for yourself, for your codebase, and for all your employees. We offer all of these options out of the box, so you can choose the mechanism that makes the most sense for you.
If there is a setting or control that is missing, or if anything is unclear from the docs, please tell us!
> We use session quality feedback as a signal to make sure Claude Code users are having a good time
Your entire answer ignores the fact that this is irritating behavior that ensures users are not having a good time. We don't want to chase down secret config values. We want to click "stop bothering me" and be done with it.
Thank you for taking the time to respond here. Thank you also for sharing your point of view, use case, and where you are coming from. With that said, would you mind sharing a few words on a couple questions?:
1. Does it take as much effort to opt-in to your feedback mechanism as it takes to opt-out? If not, why not?
2. If you want a thing ('feedback', 'a signal', data that is helpful to YOU), but getting it has this negative effect on others, what would happen if you preferenced others over yourself, and did with less of the thing?
Thank you for the feedback. I honestly believe that Claude Code is trying to be more privacy aware than other products, but it takes vigilance on both sides to get there. When you say the survey sends back more than the numeric value and add the 'etc' can you be very specific about the 'etc' is? The information you mention seems at odds with the data-usage documentation [1] which says only a numeric value is sent. Is the documentation going to be fixed to be explicit that more than a numeric value is sent? Is the feedback prompt going to ask the user if it is ok that more than a numeric value is sent back with the survey data?
Again, I think you are making the best product out there. I want to keep using it. Privacy is my #1 feature request to keep using it so transparency is crucial.
1. We use session quality feedback as a signal to make sure Claude Code users are having a good time. It's helpful data for us to more quickly spot & prevent incidents like https://www.anthropic.com/engineering/a-postmortem-of-three-.... There was a bug where we were showing the survey too often, which is now fixed (it was annoying and a misconfiguration on our part).
2. Giving session quality feedback is totally optional. When you provide feedback, we just collect your numerical rating and some metadata (like OS, terminal, etc.). Giving feedback doesn't cause us to log your conversation, code, or anything like that. (docs: https://code.claude.com/docs/en/data-usage#session-quality-s...)
3. We don't train on quality feedback data. This is documented in the link above.
4. If you don't want to give feedback, you can permanently turn it off for yourself by setting CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1 in your env or settings.json file. (docs: https://code.claude.com/docs/en/settings)
5. To permanently turn off the feedback survey for your whole company, set CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY=1 in the settings.json checked into your codebase, or in your enterprise-managed settings.json (docs: https://code.claude.com/docs/en/settings)
6. You can also opt out of both telemetry + survey by setting CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1, or you can more granularly opt out with DISABLE_ERROR_REPORTING=1, DISABLE_TELEMETRY=1, etc. (also documented in the settings docs)
Security and privacy are very important, and we spend a lot of time getting these right. You have full control over data usage, telemetry, and training, and these are configurable for yourself, for your codebase, and for all your employees. We offer all of these options out of the box, so you can choose the mechanism that makes the most sense for you.
If there is a setting or control that is missing, or if anything is unclear from the docs, please tell us!