{"version":"2.1.277","anchor":"bridge-control-requests-now-logged-with-durationdeadline-te","canonical_anchor":"bridge-control-requests-now-logged-with-durationdeadline-te","heading":"Bridge control requests now logged with duration\/deadline telemetry","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/bridge-control-requests-now-logged-with-durationdeadline-te","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Bridge control requests now logged with duration\/deadline telemetry\n\nSDK bridge now logs how long each control request took to handle, plus deadline\/timeout info\n\n**What**\n\nThe SDK bridge, which relays control requests between a client and Claude Code, now measures and logs how long each `control_request` took to process. The new telemetry event also records whether the request was \"detached\" and, when a deadline was set on the request, what that deadline was and whether it was exceeded.\n\n**Why**\n\nThis gives better visibility into bridge performance and helps diagnose slow or timed-out control requests when building on the SDK.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}