{"version":"2.1.312","anchor":"served-channel-requests-report-start-and-end","canonical_anchor":"served-channel-requests-report-start-and-end","heading":"Served channel requests now signal when they start and end","tier":"internal","area":"Served Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/served-channel-requests-report-start-and-end","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Served channel requests now signal when they start and end\n\nRequests on a served channel now trigger optional start and end signals around each request\n\n**What**\n\nWhen Claude Code serves a request on a channel, it now calls optional start and end signals around each request. Before, there were no such signals.\n\n**Why**\n\nThese signals may be used to track when Claude Code is busy and when it is idle.\n\n- Area: Served Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}