Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

SDK docs explain CLAUDE_CODE_SYNC_PLUGIN_INSTALL and managed plugin errors

SDK schema descriptions now cover background plugin installs, managed-settings plugin errors, and CI use of CLAUDE_CODE_SYNC_PLUGIN_INSTALL

Group of 2 Use it now Improvements
JSON All of v2.1.323
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.323,
What probably matters to youSection of the release

What

The Agent SDK lets programs run Claude Code without the interactive screen. Its schema descriptions, the built-in documentation for the messages it sends, were updated around plugin installation.

  • Install progress: without the environment variable CLAUDE_CODE_SYNC_PLUGIN_INSTALL, plugins install in the background. In that case the install progress messages reach only the Claude desktop app, over a local standard-output connection.
  • plugin_errors: now also reports plugins enabled by managed settings (organization-controlled settings) that failed to load. Over connections that may store messages, these entries carry one fixed sentence with no file path.
  • CI warning: a check on plugin_errors in automated testing (CI) can trip on a throwaway machine that has no copy of the plugin, and CLAUDE_CODE_SYNC_PLUGIN_INSTALL=1 makes the first turn wait for the install.

Why

If you run Claude Code in automation, background installs can make plugin errors appear that are not real failures. Setting CLAUDE_CODE_SYNC_PLUGIN_INSTALL=1 makes the first turn wait so plugins are in place before work starts.

Read from
What the documentation says

See this entry in the whole of v2.1.323 →

Feedback