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.234 ·

Managed policy helpers can be an inline script instead of an executable

Admins can now supply managed policy helpers as an inline script instead of a file on disk.

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

The admin-controlled policyHelpers config, which computes managed settings at startup, now accepts a script plus interpreter pair as an alternative to path. The script is handed to the interpreter over stdin and never written to disk. It is capped at 65536 characters, must be NUL-free valid UTF-8, and must be ASCII-only on Windows. The interpreter is fixed per operating system: sh on macOS, Linux and WSL, pwsh on Windows.

Details
  • Validation now requires each entry to carry path, or script + interpreter, and/or defaultSettings (a static settings payload); mixing path with script is rejected.
  • Inline scripts only work on the per-OS policyHelpers map. On the older singular policyHelper key they are refused with "inline scripts are not supported on the singular policyHelper key".
  • Execution is /bin/sh -s over stdin, or pwsh with -Command wrapping the script in a fixed fragment ending catch { Write-Error $_; exit 1 }; exit $LASTEXITCODE.
  • No feature flag guards the parser; it is reachable for anyone whose admin-controlled policy settings carry such an entry. None of this vocabulary existed in v2.1.233.
Evidence

Inline helper script, delivered to the fixed interpreter over stdin (never written to disk), inline scripts are not supported on the singular policyHelper key

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

Read from
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.

Confirmed since Anthropic's documentation has since written up interpreter, on Configure auto mode. By default, narrow Bash and PowerShell allow rules such as `Bash(npm test)` stay in effect in auto mode. Claude Code resolves them before the classifier runs, unless the command carries [per-command allowed domains](/docs/en/sandboxing#per… auto-mode-config see the edit
Added since A small documentation edit on Changelog touched a line naming script after this was published. <Update label="Known issue: Cowork on Windows" description="2026-09-10"> cowork/changelog see the edit
Confirmed since Anthropic's documentation has since written up script, on MCP, plugins, skills, and hooks. | `.claude-plugin/plugin.json` | **Required.** Plugin manifest (name, description, version). Directories without this file are ignored. | third-party/claude-desktop/extensions 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 script, on MCP, plugins, skills, and hooks.

See this entry in the whole of v2.1.234 →

Feedback