{"version":"2.1.314","anchor":"analytics-event-export-moved-off-axios-onto-bunfetchsession","canonical_anchor":"analytics-event-export-moved-off-axios-onto-bunfetchsession","heading":"Usage data is now sent with a different network method","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/analytics-event-export-moved-off-axios-onto-bunfetchsession","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Usage data is now sent with a different network method\n\nClaude Code now sends its usage data through Bun's own network connection, without following redirects and with proxy and certificate settings applied\n\n**What**\n\nClaude Code sends usage data (records of how it is used) to Anthropic. That sending now goes through a network connection built into Bun, the runtime Claude Code runs on, instead of a separate networking library. It does not follow redirects, and it applies your proxy and TLS settings. TLS is the encryption and certificate checking on a connection.\n\nWhere the runtime has no such connection, sending fails with \"this runtime has no Bun.FetchSession\".\n\n**Why**\n\nIf you use a proxy or custom certificates, this changes how that traffic is routed and checked.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}