Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.293 ·

New managed settings for Claude Desktop admins: default model, model catalog and more

Admins of third-party Claude Desktop deployments get managed settings for default model effort, model catalog and Chrome password managers

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

The managed configuration for third-party Claude Desktop deployments has new keys. Managed configuration means settings an administrator sets centrally for everyone in an organisation.

  • defaultModelEffort
  • alwaysStartWithDefaultModel
  • modelCatalogEnabled
  • modelCatalogUrl
  • claudeInChromePasswordManagersEnabled, whose value comes from the server

Several keys are now marked as applying to the desktop app, and the schema description mentions x-executionTarget. The help for otlpTracesEnabled now says that, when otlpEndpoint is set, this setting alone decides whether traces are exported. Scanning of the credential store also skips its own set of names at the top level of the store.

Why

Administrators of these Desktop deployments get more control over which model people start with and which models they can pick. This is Desktop configuration code that ships inside Claude Code, so it matters mostly to Desktop admins rather than to command-line users.

See this entry in the whole of v2.1.293 →

Feedback