{"version":"2.1.274","anchor":"request-telemetry-gains-rawrequestbodyid-and-a-requestbodyid","canonical_anchor":"request-telemetry-gains-rawrequestbodyid-and-a-requestbodyid","heading":"Request telemetry gains rawRequestBodyId and a requestBodyId threaded into assistant-response logging","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/request-telemetry-gains-rawrequestbodyid-and-a-requestbodyid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Request telemetry gains rawRequestBodyId and a requestBodyId threaded into assistant-response logging\n\nAssistant-response logging now threads a requestBodyId through the telemetry that records completions\n\n**What**\n\nThe internal function that logs completion telemetry now takes and passes along a `rawRequestBodyId` value (previously stored under a differently named slot), and forwards a `requestBodyId` into the code path that saves assistant responses.\n\n**Why**\n\nThis is internal bookkeeping for how Claude Code correlates a logged response with the request that produced it. It has no direct effect on how you use the tool.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}