{"version":"2.1.268","anchor":"sdk-bridge-permission-requestnotification-handling-hardened","canonical_anchor":"sdk-bridge-permission-requestnotification-handling-hardened","heading":"SDK bridge permission_request\/notification handling hardened","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/sdk-bridge-permission-requestnotification-handling-hardened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### SDK bridge permission_request\/notification handling hardened\n\nSDK bridge handles permission requests and malformed notifications more defensively\n\n**What**\n\nThe SDK bridge (the layer that lets an external host application talk to Claude Code) now handles a few edge cases more carefully:\n\n- Errors while handling a permission request are now caught and logged instead of crashing unhandled.\n\n- Notification messages whose `method` field isn't a string are now dropped with a warning instead of being passed through.\n\n- Permission request messages are now validated with proper type checks on their `tool_use_id` and `request_id` fields, fixing what looks like a latent bug where the check referenced an undefined variable and so never worked as intended.\n\n**Why**\n\nThese changes make the SDK bridge more robust against malformed or unexpected messages, preventing crashes and silently-broken validation.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}