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.235 Home All releases ←olderv2.1.234 v2.1.236newer→
Claude Code v2.1.235

Managed settings track whether a policy helper was armed remotely

Under the hood
Useful2 Signal3
Settings

Settings can now show "Enterprise managed settings (remote helper)" when a policy helper was armed remotely.

What

The settings machinery now distinguishes a policy helper armed by remote settings from a locally configured one, and the settings-source label can read "Enterprise managed settings (remote helper)".

Details
  • The resolver returns the helper plus a remoteArmed flag, defaulting to true unless the source says otherwise, and the reported tier becomes "remote" rather than "helper" in that case.
  • The helper store gained fields tracking the remote arming generation, its config and the notice subject; tier changes are announced through a dedicated method rather than an ad-hoc callback.
  • policyHelpers joins the recognised helper settings alongside gcpAuthRefresh, otelHeadersHelper, processWrapper, proxyAuthHelper, statusLine and subagentStatusLine, and origin is now derived from the settings source.
  • The shell-environment fingerprint expands policyHelpers into per-OS entries with a hashed value rather than listing the bare key.
Evidence

Enterprise managed settings (remote helper), policyHelpers., policyHelpers

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

See this entry in the whole of v2.1.235 →