{"version":"2.1.300","anchor":"gateway-inference-settings-are-now-read-by-claude-code-cod","canonical_anchor":"gateway-inference-settings-are-now-read-by-claude-code-cod","heading":"Claude Code now reads many shared managed settings used by Desktop","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/gateway-inference-settings-are-now-read-by-claude-code-cod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Claude Code now reads many shared managed settings used by Desktop\n\nGateway, Bedrock, Vertex, OTLP telemetry, attribution and tool policy settings in the shared managed config now list Claude Code as a reader\n\n**Unclear.** It is not confirmed that Claude Code acts on these settings yet, only that they now list it as a reader.\n\n**What**\n\nSome settings live in a shared, centrally managed configuration that several Anthropic apps read. Each setting lists its readers, such as \"desktop\" or \"m365\". Many now also list \"code\", meaning Claude Code:\n\n- Gateway and inference: `inferenceGatewayBaseUrl`, `inferenceStreamIdleTimeoutSec`, `isLocalDevMcpEnabled`, `inferenceCustomHeaders`, `inferenceFoundryResource`, and the inference credential helper. The credential helper also lost its `executionTarget: \"desktop\"` restriction.\n\n- Amazon Bedrock and Google Vertex: `inferenceBedrockBaseUrl`, `inferenceBedrockRegion`, `inferenceBedrockProfile`, `inferenceBedrockAwsDir`, and the Vertex project ID.\n\n- Telemetry export over OTLP: `otlpTracesEnabled`, `otlpProtocol`, `otlpAuthMode` and `otlpContentCapture`.\n\n- Other: `endUserAttribution`, `scheduledTasksEnabled` and `builtinToolPolicy`.\n\nBefore, these were read only by \"desktop\", or by \"desktop\" and \"m365\". A new `activatesThirdPartyMode` export was also added. A new message reads \"To sandbox sessions, set sandbox.enabled to true in settings.\", referring to `sandbox.enabled`. For the OTLP and attribution settings, the change seen is in the schema only.\n\n**Why**\n\nOrganisations that manage Desktop through this configuration, for example to route requests through their own gateway or cloud provider or to export telemetry, can drive Claude Code from the same settings.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}