{"version":"2.1.274","anchor":"request-id-validated-with-a-strict-pattern-in-control-protoc","canonical_anchor":"request-id-validated-with-a-strict-pattern-in-control-protoc","heading":"request_id validated with a strict pattern in control-protocol payloads","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/request-id-validated-with-a-strict-pattern-in-control-protoc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### request_id validated with a strict pattern in control-protocol payloads\n\nBridge control-protocol messages now validate request_id against a strict pattern before forwarding it\n\n**What**\n\nClaude Code's bridge control-protocol message handling now includes a helper that only forwards a `request_id` field if it matches the pattern `req_` followed by 4 to 128 letters, digits, underscores, or hyphens. A companion helper checks whether a JSON payload textually contains a given key.\n\n**Why**\n\nValidating the shape of `request_id` before forwarding it guards against malformed or unexpected values being passed through the bridge's control-protocol messages.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}