{"version":"2.1.268","anchor":"feedback-survey-followup-payload-now-whitelists-included-tra","canonical_anchor":"feedback-survey-followup-payload-now-whitelists-included-tra","heading":"Feedback survey followup payload now whitelists included transcript\/session fields","tier":"internal","area":"Feedback","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/feedback-survey-followup-payload-now-whitelists-included-tra","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Feedback survey followup payload now whitelists included transcript\/session fields\n\nFeedback survey followups now send only a fixed, named list of fields instead of a free-form object\n\n**What**\n\nWhen you submit a followup to a feedback survey, Claude Code now builds the data it sends from a fixed list of named fields: `latestAssistantMessageId`, `message_count`, `datetime`, `description`, `surface`, `platform`, `gitRepo`, `commitSha`, `remoteWorkspace`, `remoteSessionId`, `version`, `transcript`, `subagentTranscripts`, `rawTranscriptJsonl`, `recentSessionTranscripts`, and `debugLog`. Previously the submission passed through whatever object it was given.\n\n**Why**\n\nRestricting the payload to a known allowlist of fields prevents unintended or extra data from being included in a feedback submission.\n\n- Area: Feedback\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}