{"version":"2.1.310","anchor":"feedback-survey-events-gain-followup-fields-logs-followup-c","canonical_anchor":"feedback-survey-events-gain-followup-fields-logs-followup-c","heading":"Feedback survey: follow-up text results and a narrower every_rating","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/feedback-survey-events-gain-followup-fields-logs-followup-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Feedback survey: follow-up text results and a narrower every_rating\n\nThe feedback survey can now report follow-up text results with a logs_followup signal, and every_rating needs one more condition\n\n**What**\n\nAfter you rate a response, Claude Code can show a feedback survey with a box for more comments. A host is an app that runs Claude Code inside it, such as an editor. Several pieces of this changed:\n\n- Follow-up details: the survey record a host sends now carries `followup_box`, `no_followup_reason`, `char_count`, `error_code` and `saved_locally`.\n\n- Follow-up events: `followup_text_submitted` and `followup_text_failed` are now accepted, and are handled before the usual survey check.\n\n- `logs_followup`: a new field tells hosts whether this version logs the `followup_*` survey events they send. The feedback and transcript-sharing information now always includes `logs_followup: true`.\n\n- `every_rating`: this value, which marks every rating for collection, now needs one more value to be present on top of the `tengu_curried_sparrow` server switch.\n\nThe previous release built `tengu_curried_sparrow` as off by default, and no reading has been taken under this release yet.\n\n**Why**\n\nAn editor's feedback box can now report whether follow-up text was sent, saved or failed. Every rating is marked for collection in fewer cases than before.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}