{"version":"2.1.323","anchor":"traceparent-header-on-proxy-requests-web-fetch-gets-context","canonical_anchor":"traceparent-header-on-proxy-requests-web-fetch-gets-context","heading":"Proxy requests carry a tracing header, and web fetches get conversation context","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/traceparent-header-on-proxy-requests-web-fetch-gets-context","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Proxy requests carry a tracing header, and web fetches get conversation context\n\nRequests through the proxy to `\/worker\/` now include a `traceparent` header, and WebFetch is given the turn's messages and compaction point\n\n**What**\n\nRequests Claude Code sends through its proxy to `\/worker\/` addresses now include a `traceparent` header when one is available. A `traceparent` header is a standard label that lets a request be followed across systems for tracing.\n\nThe WebFetch tool, which fetches web pages, is now also given the current turn's messages and the point at which the conversation would be automatically compacted (summarised to save space).\n\n**Why**\n\nRequests are easier to trace, and web fetching can take the size of the conversation into account.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}