{"version":"2.1.309","anchor":"ccr-sender-address-prefetch-workersender-addr-is-wired-i","canonical_anchor":"ccr-sender-address-prefetch-workersender-addr-is-wired-i","heading":"Remote sessions can fetch a signed copy of the client's IP address","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/ccr-sender-address-prefetch-workersender-addr-is-wired-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Remote sessions can fetch a signed copy of the client's IP address\n\nIn remote cloud sessions, Claude Code can fetch a signed copy of the client's IP address and keep it ready for later requests\n\n**Unclear.** It is not clear when the two conditions are met or whether the stored headers are ever sent with a request.\n\n**What**\n\nIn remote cloud sessions, Claude Code can ask the cloud session service for a signed copy of the client's IP address (the network address the connection comes from). It signs in to that service with the session's own credentials. It keeps the result to reuse within the same run, stored as two request headers, which are labels attached to a web request:\n\n- `x-ssr-client-ip`: the IP address\n\n- `x-ssr-client-ip-sig`: a signature that proves the address came from the service\n\nThe fetch happens while a request is being set up, and only when two conditions inside Claude Code are met. At that point it only fills the stored copy and does not attach the headers to anything.\n\n**Why**\n\nThis is part of how remote sessions run and is unlikely to be visible when you use Claude Code on your own computer. It suggests the service will be able to check which address a request really came from.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}