Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.281entry #464

Claude Code v2.1.281 ·

Desktop managed-config schema: new 'ask-session' tool policy and version-support tags

The desktop managed-config schema now tags ask-session and several other settings with the app version that supports them

Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
What

The settings schema describes which managed settings an organization can set for the desktop app. It now records the minimum app version for several of them:

  • ask-session tool policy value: from 1.21459.0.
  • "Helper cache TTL (sec)": from 1.21459.0.
  • "Default for tier": from 1.13576.0.
  • broker value for inferenceFoundryAuthFlow: from 1.24012.0.
  • The headers-helper refresh buffer and additionalRedirectReferrerHosts: now carry version gates too.

A constant SSH_CLIENT_UNREADABLE_STAND_IN with the value "/dev/null/unreadable-ssh-client" is also added.

Why

Admins can see which app version is needed before a setting or value takes effect, so a policy is not set for a version that cannot use it.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what `SSH_CLIENT_UNREADABLE_STAND_IN` is used for.

See this entry in the whole of v2.1.281 →

Feedback