Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Remote managed settings fetch: public-address gateway refusal and richer diagnostics

Fetching remote managed settings now refuses gateways that resolve to a public address and reports more about failures

You'll notice Improvements
JSON All of v2.1.281
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What

Remote managed settings are settings an organisation's administrator publishes, which Claude Code downloads. When Claude Code goes through a cloud gateway to get them (a gateway is a go-between server that forwards requests), it now refuses if the gateway's address lies outside the network where it was verified. That fails with errorKind gateway_public_address and is not retried. The error text reads "Cloud gateway connection outside the network it was checked on".

The fetch result also reports more detail:

  • authType, credentialOrigin, and tokenRefreshOutcome (OAuth sign-in only)
  • errno on timeouts and network errors
  • retriedAfter401 and forcedRefreshOutcome after a forced token refresh

When the credentials carry no pin fingerprint, a verified hostVerdict can now supply the secure connection. The User-Agent header, which identifies the client to the server, changes when both CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST and CLAUDE_CODE_USE_GATEWAY are set.

Why

If a gateway unexpectedly points somewhere public, Claude Code now stops instead of sending the request there. When fetching settings fails, the extra details make it easier to see whether sign-in, credentials or the network was the problem.

See this entry in the whole of v2.1.281 →

Feedback