{"version":"2.1.310","anchor":"session-access-token-marked-on-http-agent-options","canonical_anchor":"session-access-token-marked-on-http-agent-options","heading":"Requests using a session access token are now marked when sent through a proxy","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/session-access-token-marked-on-http-agent-options","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Requests using a session access token are now marked when sent through a proxy\n\nRequests sent with CLAUDE_CODE_SESSION_ACCESS_TOKEN now carry a marker saying they hold Claude Code's own token when they go through a proxy\n\n**Unclear.** It is not clear what the new marker changes about how the token is sent through a proxy.\n\n**What**\n\nWhen Claude Code sends requests using the token in `CLAUDE_CODE_SESSION_ACCESS_TOKEN`, the connection settings it builds for a proxy now include a marker saying the request carries Claude Code's own token. A proxy is a server on your network that relays traffic between your computer and the internet. Before, those connection settings were built without that marker.\n\nIn the same release, proxy tunnel errors with the code 407, which a proxy returns when it wants you to log in to it, are now handled through one shared piece of code.\n\n**Why**\n\nIf you run Claude Code with `CLAUDE_CODE_SESSION_ACCESS_TOKEN` behind a proxy, this changes how that token's requests are set up on their way out.\n\n- Area: Internals\n- Names: `CLAUDE_CODE_SESSION_ACCESS_TOKEN`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}