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

Claude Code v2.1.235 ·

Managed-settings policy helper can be "armed from remote"

Managed-settings policy helpers can now be armed from a remote source, reported as a distinct settings tier and fingerprinted per OS

Under the hood Improvements
JSON All of v2.1.235
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Policy HelpersArea: what it touches
ImprovementsKind: in v2.1.235,
ImprovementsSection of the release

The policy-helper resolver now returns { helper, remoteArmed }, with remoteArmed defaulting to true unless the source says otherwise. When armed remotely, the reported settings tier shows as "remote" instead of "helper", and the settings-source display can read "Enterprise managed settings (remote helper)" as a distinct case from the local helper or default payload. The helper store gained remoteArmGeneration, remoteArmingConfig and remoteNoticeSubject, and tier changes now go through a dedicated method rather than an ad-hoc callback.

policyHelpers joins the recognised helper settings list alongside gcpAuthRefresh, otelHeadersHelper, processWrapper, proxyAuthHelper, statusLine and subagentStatusLine. The policy-origin resolver now derives origin from the settings source, including a new helperArmedFromRemote source and an armedFromRemote field on the managed-settings snapshot. The shell-environment fingerprint now expands policyHelpers into per-OS entries with a hashed value (policyHelpers.<os>=<hash>) instead of a bare key.

See this entry in the whole of v2.1.235 →

Feedback