Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Managed settings accept per-OS policyHelpers

Use it now
Useful3 Signal3
Managed Settings Notable not in their notes

Admins can set a different policy helper program per operating system with a new policyHelpers setting.

policyHelperspolicyHelper
What

Settings now take a policyHelpers object keyed by macos, linux, windows and wsl, alongside the existing single policyHelper. A bad individual entry is ignored with a status warning, but a structurally invalid policyHelpers object coming from an OS-admin policy source stops startup.

Details
  • WSL falls back to the linux entry under some conditions.
  • If no entry matches the current platform and there is no singular policyHelper fallback, a warning is emitted and no helper runs.
Evidence

"policyHelpers" could not be parsed: expected an object mapping OS keys

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.228 →