{"version":"2.1.219","anchor":"remote-control-now-explains-exactly-which-endpoint-setting-b","canonical_anchor":"remote-control-now-explains-exactly-which-endpoint-setting-b","heading":"Remote Control now explains exactly which endpoint setting blocks it","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/remote-control-now-explains-exactly-which-endpoint-setting-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Remote Control now explains exactly which endpoint setting blocks it\n\nWhen Remote Control refuses, it now names the exact setting or variable blocking it.\n\n**What**\n\nThe one-line refusal about Remote Control needing api.anthropic.com is now followed by a diagnosis of the specific configuration in play.\n\n**Details**\n\n- Separate sentences for gateway sessions, Bedrock\/mantle, and a custom `ANTHROPIC_BASE_URL`, each naming the environment variable to unset.\n- Explicitly notes that the assume-first-party escape hatch does not lift the restriction.\n\n**Evidence**\n\n`_CLAUDE_CODE_ASSUME_FIRST_PARTY_BASE_URL does not apply to Remote Control.`\n\n- Area: Remote Control\n- Names: `ANTHROPIC_BASE_URL`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}