{"version":"2.1.319","anchor":"new-telemetry-event-names-and-server-refused-feedback-state","canonical_anchor":"new-telemetry-event-names-and-server-refused-feedback-state","heading":"Groundwork for voice calls, refused feedback and permission stops","tier":"internal","area":"Voice","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/new-telemetry-event-names-and-server-refused-feedback-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Groundwork for voice calls, refused feedback and permission stops\n\nNew internal names point to voice-call and refused-feedback work, and the result output gains a stopped_by_permission_check field\n\n**Unclear.** It is not clear whether any of these are reachable, including whether the `stopped_by_permission_check` field is ever filled in.\n\n**What**\n\nThis release adds several internal names:\n\n- New usage-report events for voice-call talking and for continuing without saving.\n\n- A session marker that records when the server refused feedback.\n\n- A `stopped_by_permission_check` field in the result output, which is the summary Claude Code produces when a run ends.\n\n**Why**\n\nThese suggest work in progress on voice calls and on handling feedback the server will not accept. None of them is a feature you can use yet.\n\n- Area: Voice\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}