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 ·

Desktop app can start its Claude Code through a corporate launcher

A new managed setting, claudeCodeProcessWrapperEnabled, makes the desktop app start Claude Code through the launcher named in processWrapper

Use it now Notable New Features
JSON All of v2.1.293
Use it nowTier: how much it should matter to you
5Useful: 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 Claude desktop app has a new managed configuration key, claudeCodeProcessWrapperEnabled. Managed configuration means settings an organization's administrator pushes to its devices. When the key is turned on, the desktop app starts its bundled copy of Claude Code through a launcher program instead of running it directly. A launcher is a program your organization supplies that wraps another program as it starts. The app takes the launcher from the device's processWrapper setting or from env.CLAUDE_CODE_PROCESS_WRAPPER.

The key is off by default and has these limits:

  • Code tab sessions and the app's short runs go through the launcher
  • Cowork sessions do not go through the launcher
  • macOS and Linux only; Windows ignores the key

The app also has a new administrator-only key that copies earlier sessions from a third-party setup into the first-party profile after sign-in. It runs once per account and organization.

Why

Organizations that already require a corporate launcher for Claude Code on the command line can now apply the same launcher to the Claude Code the desktop app runs.

Read from
What the documentation says

See this entry in the whole of v2.1.293 →

Feedback