{"version":"2.1.268","anchor":"tui-opt-out-reason-now-goes-through-the-feedback-pipeline-n","canonical_anchor":"tui-renderer-opt-out-reason-now-submitted-as-feedback-not-j","heading":"TUI opt-out reasons now submitted as feedback instead of raw telemetry","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/tui-opt-out-reason-now-goes-through-the-feedback-pipeline-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### TUI opt-out reasons now submitted as feedback instead of raw telemetry\n\nWhen you opt out of the new fullscreen TUI and explain why, that reason is now sent as proper feedback, not just analytics\n\n**Unclear.** Whether telemetry previously included the raw text is not stated; nothing has been read yet about how the `tengu_tui_optout_reason` gate itself is set.\n\n**What**\n\nWhen a user opts out of the new fullscreen\/TUI (terminal user interface) renderer and types a reason, Claude Code now submits that full reason text through its feedback-submission system (with a timeout, credentials, and a character cap), recording whether the submission succeeded.\n\nAfterward, it still sends a `tengu_tui_optout_reason` telemetry event, but that event now only carries a `reason_length` and a `feedback_id` (when submission succeeded) rather than the raw reason text itself.\n\n**Why**\n\nThis keeps the actual free-text explanation out of analytics events, while still making sure it reaches the team as a proper piece of feedback rather than just an anonymized data point.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}