When Remote Control refuses, it now names the exact setting or variable blocking it.
What's wrong with this entry?
The one-line refusal about Remote Control needing api.anthropic.com is now followed by a diagnosis of the specific configuration in play.
- Separate sentences for gateway sessions, Bedrock/mantle, and a custom
ANTHROPIC_BASE_URL, each naming the environment variable to unset. - Explicitly notes that the assume-first-party escape hatch does not lift the restriction.
_CLAUDE_CODE_ASSUME_FIRST_PARTY_BASE_URL does not apply to Remote Control.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.