{"version":"2.1.306","anchor":"helper-jmn-first-party-no-anthropic-unix-socket-plus-two","canonical_anchor":"helper-jmn-first-party-no-anthropic-unix-socket-plus-two","heading":"A check that stays false when ANTHROPIC_UNIX_SOCKET is set","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.306\/e\/helper-jmn-first-party-no-anthropic-unix-socket-plus-two","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.306","markdown":"### A check that stays false when ANTHROPIC_UNIX_SOCKET is set\n\nClaude Code has a check that is true only for direct Anthropic API access with ANTHROPIC_UNIX_SOCKET unset, plus two further internal conditions\n\n**Unclear.** It is not clear whether anything calls this check, so what it controls for a reader is unknown.\n\n**What**\n\nClaude Code contains a check that answers yes only when all of these hold:\n\n- the API provider is Anthropic itself, rather than a third-party cloud provider\n\n- the `ANTHROPIC_UNIX_SOCKET` environment variable is not set (an environment variable is a named value you set in your shell before starting a program)\n\n- two further internal conditions are met\n\nIf any part of the check fails with an error, Claude Code logs the error and treats the answer as no. No place in Claude Code that uses this check was found, so it is not known what it turns on or off.\n\n**Why**\n\nThe check reads like a way to keep something switched off for people who send their API traffic through a custom Unix socket, which is a local connection point set with `ANTHROPIC_UNIX_SOCKET`. Until something uses it, it changes nothing you can see.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}