{"version":"2.1.319","anchor":"stream-event-hold-gets-sethassubscribers","canonical_anchor":"stream-event-hold-gets-sethassubscribers","heading":"Groundwork for remote and voice features in how Claude Code streams events","tier":"internal","area":"Voice","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/stream-event-hold-gets-sethassubscribers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Groundwork for remote and voice features in how Claude Code streams events\n\nClaude Code can now track whether anything is listening to its event stream, and remote sessions recognise a voice-call origin\n\n**Unclear.** Whether any of this is switched on, or changes anything a user can see, has not been determined.\n\n**What**\n\nWhile it works, Claude Code sends out a stream of events describing what is happening. Several small pieces were added around that stream:\n\n- Listener tracking: Claude Code can now be told whether anything is listening to the stream.\n\n- Hold time: when nobody is listening, events are held for a separate length of time.\n\n- Voice calls: remote session code recognises messages that come from a voice call and treats them as produced by the host app rather than typed by you.\n\n- Connector flag: events can be marked as coming from a connector, and that mark is combined across events.\n\n**Why**\n\nThese are small building blocks that point toward remote and voice features.\n\n- Area: Voice\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}