Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Managed settings in host-managed gateway sessions: merge by default and no disk cache

In host-managed gateway sessions, parentSettingsBehavior defaults to merge and remote managed settings are no longer cached on disk

Group of 2 You'll notice Improvements
JSON All of v2.1.281
You'll noticeTier: how much it should matter to you
3Useful: 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

Managed settings are policies an organisation pushes to Claude Code. A host-managed gateway session is one where both CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST and CLAUDE_CODE_USE_GATEWAY are set. In these sessions, managed settings now behave differently.

  • parentSettingsBehavior controls whether restrictions passed in by an embedding host, such as the Claude Desktop app, are dropped or merged in. When a managed settings source does not set it, it now defaults to "merge" in a host-managed gateway session with a qualifying entrypoint, such as Claude Desktop's Code tab. Everywhere else it stays "first-wins". The setting's description was updated to match. Before, merging happened only when it was set to "merge" explicitly, or when there were no other managed settings at all.
  • Remote managed settings are no longer saved to disk in these sessions unless CLAUDE_CODE_REMOTE_SETTINGS_PATH is set. Reading the disk cache and preparing the storage backend also return early.
  • When the server replies that the settings have not changed, Claude Code skips writing the signature and skips the reset check under the same condition.
  • Each attempt to sign in for the settings fetch is now labelled with its sign-in method: gateway_jwt, oauth, api_key, profile or none. The gateway fingerprint is only worked out when the token is pinned.

Why

For Claude Desktop gateway users, the host's restrictions now combine with the organisation's policy by default instead of being dropped. These deployments also stop leaving a copy of the organisation's settings on disk.

Read from
Names in the bundleparentSettingsBehavior
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Deploy Claude apps gateway on AWS touched a line naming parentSettingsBehavior after this was published. The gateway is now running, but developers can't reach it from `/login` until the gateway URL is on their machines. Deploy the full [managed settings snippet](/docs/en/claude-apps-gateway#set-the-gateway-url), with `forceLoginMethod`, `for… claude-apps-gateway-on-aws see the edit
Confirmed since Anthropic's documentation has since written up parentSettingsBehavior, on Configuration reference. Scoped `Bash(…)` rules apply in Code sessions only; Cowork's shell follows only a bare `Bash` entry. Start absolute file paths with `//`, not `/`: a relative pattern such as `Read(**/.env)` covers only a Code session's project folder and n… third-party/claude-desktop/configuration see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up parentSettingsBehavior, on Configuration reference.

See this entry in the whole of v2.1.281 →

Feedback