Auto mode server checks prepared for host-managed gateway providers
Claude Code adds groundwork for server-side auto mode checks when a host such as Claude Desktop manages the provider gateway, plus gateway login reporting
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
GatewaysArea: what it touches
ImprovementsKind: in v2.1.315,
What probably matters to youSection of the release
What
Auto mode is a permission mode where Claude Code checks each action and decides whether it can go ahead without asking you. CLAUDE_CODE_AUTO_MODE_SERVER controls whether Claude Code asks Anthropic's server to do that review. New code extends this to setups where Claude Code reaches the model through a third-party provider whose connection is managed by a host program:
A new check for third-party providers needs all three of: CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST set, a per-user server-classifier switch (cached by Claude Code) being on, and CLAUDE_CODE_AUTO_MODE_SERVER.
Claude Code logs whether each server check came back with a verdict or without one.
Gateway details are now built from the host-managed provider: the gateway's address (gatewayHost) and whether the desktop app turned the check on (desktopTurnedCheckOn).
A separate forced-login function reports a gateway address that was named by an "administrator" or a "developer", and also covers internal networks.
Why
In practice, setups where a gateway (a go-between server that forwards requests to the model) is managed by a host such as the desktop app gain wiring for server-side auto mode review and for reporting who set the gateway login. The members show the plumbing, not what users see yet.
