{"version":"2.1.286","anchor":"user-agent-header-added-to-domain-info-preflight-and-self-ho","canonical_anchor":"user-agent-header-added-to-domain-info-preflight-and-self-ho","heading":"More Claude Code requests now identify themselves with a User-Agent","tier":"internal","area":"API Requests","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/user-agent-header-added-to-domain-info-preflight-and-self-ho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### More Claude Code requests now identify themselves with a User-Agent\n\nMany of Claude Code's own network requests, including the web page safety check and sign-in lookups, now send a `User-Agent` header\n\n**Unclear.** The exact value Claude Code sends in the header is not stated.\n\n**What**\n\nA `User-Agent` header is a line in a web request that says which program sent it. Claude Code now adds one to several requests that used to send none:\n\n- the domain safety check before fetching a web page\n\n- requests from self-hosted runners\n\n- session ingress fetches and saving sessions\n\n- the list of claude.ai connectors\n\n- sign-in profile and user-role lookups, and other sign-in request headers\n\n- requests through the Claude Code remote proxy\n\nThe request that lists peer sessions no longer sets its own `User-Agent` header.\n\n**Why**\n\nServers can now tell which of these requests come from Claude Code. If you run a proxy or firewall that filters by `User-Agent`, these requests will look different.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}