{"version":"2.1.280","anchor":"remote-session-response-posting-gets-an-optional-post-listen","canonical_anchor":"remote-session-response-posting-gets-an-optional-post-listen","heading":"Remote session response posting gets an optional post-listener with timing","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-session-response-posting-gets-an-optional-post-listen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Remote session response posting gets an optional post-listener with timing\n\nRemote session responses can now trigger a post-send listener that reports timing, without affecting delivery\n\n**What**\n\n`RemoteSessionManager.sendResponse`, which sends control responses for remote sessions, now accepts an optional callback that runs after the response is sent, passing it the response and how many milliseconds it took. If that callback throws an error, the error is caught and logged, but it does not affect whether the response was actually delivered.\n\n**Why**\n\nThis lets other parts of Claude Code observe timing on remote session responses without risking breaking the response delivery itself if that observation code has a bug.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}