Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SurveysArea: what it touches
Internal ChangesKind: in v2.1.304,
What probably matters to youSection of the release
Unclear It is not clear what makes this survey appear, so whether anyone sees it is unknown.
What
Claude Code gains a survey that an organisation can send to its members:
It fetches a pending survey from an organisation survey service, then records milestones, dismissals and submissions.
The survey has select, multi-select and text questions, then a review step that says answers won't be used to improve Anthropic's services.
It runs only for people signed in directly with Anthropic on an enterprise subscription, and is skipped when CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY is set.
Checks for a new survey are spaced out using a stored orgSurveyCheck.nextCheckAt, every 6 hours by default.
The survey area above the prompt gains an orgSurvey card with start, dismiss and ignore actions, wired in next to the memory, feedback and frustration surveys. The only trigger found is an entry { survey: "orgSurvey", passiveCard: "open" }.
The feature is controlled by the server flag tengu_steady_mitten, whose built-in fallback value is false, so it shows only where the server enables it. The same release also adds a low_resource_notice name to a list of notices.
Why
If you are on an enterprise plan, your organisation may be able to ask you questions inside Claude Code. Setting CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY keeps it away along with the other surveys.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what makes this survey appear, so whether anyone sees it is unknown.
