{"version":"2.1.323","anchor":"new-protocol-capability-strings","canonical_anchor":"new-protocol-capability-strings","heading":"Voice-call notes gain a capability check and are hidden from view","tier":"internal","area":"Protocol","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-protocol-capability-strings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Voice-call notes gain a capability check and are hidden from view\n\nVoice-call notes now go only to processes listing voice_call_talk_line_v1, and user messages from a voice call are hidden in a visibility check\n\n**What**\n\nClaude Code already recognised messages marked as notes of what was said aloud on a voice call. This release adds rules around them.\n\n- New capabilities: `voice_call_talk_line_v1` and `withdrawn_files_note_v2` are added to the list of capabilities a Claude Code process announces, after `start_shell_task_v1`.\n\n- Capability requirement: the description for voice-call notes now says to send a note only to a process that lists `voice_call_talk_line_v1`. Such a process stores the note in a form older builds do not send to a model, and sends no note to the Remote Control event lane.\n\n- Hidden messages: a check that decides which messages are shown now hides user messages whose origin is `voice-call`.\n\n**Why**\n\nThis is continuing groundwork for using Claude Code alongside a voice call. For programs built on Claude Code, it sets out which processes may receive voice-call notes, so older builds are not sent notes they would pass on to the model.\n\n- Area: Protocol\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 5\/5\n- Scope: individual\n- Heads-up: no"}