{"version":"2.1.286","anchor":"bridge-session-create-request-drops-user-agent-header","canonical_anchor":"bridge-session-create-request-drops-user-agent-header","heading":"One remote session request no longer sends a User-Agent header","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/bridge-session-create-request-drops-user-agent-header","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### One remote session request no longer sends a User-Agent header\n\nA request Claude Code sends to a remote server no longer includes the User-Agent header that names the client program\n\n**Unclear.** It is not settled exactly which request this is, though it appears to be the one that creates a remote bridge session.\n\n**What**\n\nOne request Claude Code sends to a remote server no longer carries a `User-Agent` header. That header is the line in a web request that identifies which program sent it. The request still sends:\n\n- the `anthropic-beta` header\n\n- the `x-organization-uuid` header\n\n- the trusted-device token\n\n**Why**\n\nAnything on the server side that logs or recognises clients by their `User-Agent` will no longer see it on this request.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}