Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

SDK can send managed settings at startup instead of on the command line

A new SDK option, managedSettingsDelivery, lets managed settings be sent with the startup request and ends the session if they are not confirmed

Use it now Notable No documentation found New Features
JSON All of v2.1.323
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
New FeaturesKind: in v2.1.323,
What probably matters to youSection of the release
What

The SDK, the toolkit programs use to run Claude Code, has a new option, managedSettingsDelivery. Managed settings are settings an organization enforces centrally. The option takes one of two values:

  • 'argv', the default, passes the managed settings on the command line when Claude Code starts.
  • 'initialize' sends them in the first request the SDK makes to start the session.

With 'initialize', if Claude Code does not confirm that it applied the managed settings, the session is ended. Any other value is rejected as invalid. A matching option, managedSettingsInInitialize, also appears among the options for print mode.

Why

Programs built on the SDK can now deliver managed settings through the startup request. Because the session ends when they are not confirmed, a session never runs without them by accident.

Read from
Names in the bundlemanagedSettingsDelivery
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed the Agent SDK's managedSettings ignoring the Remote Control, agent view, Workflows and Artifact off switches

See this entry in the whole of v2.1.323 →

Feedback