Claude Code Update: What Changed in v2.1.323

Claude Code Update: What Changed in v2.1.323

  • Code Mode lets Claude call tools using JavaScript.
  • Plugins install only when their Claude Code version range is met.
  • Background sessions stop when their authentication details do not match.

Claude Code v2.1.323 adds experimental Code Mode and plugin version range checks, and changes how background sessions handle authentication. These updates matter to people who build or use plugins, work with models that require usage credits, or run background tasks under multiple login profiles.

Experimental Code Mode in the Claude Code update

Claude Code Update: What Changed in v2.1.323

Claude Code v2.1.323 adds Code Mode as an experimental option. When it is enabled, Claude writes JavaScript to call tools.

The Code Mode documentation explains how to turn it on and how an organization can disable it. Both individual users who want to try the mode and administrators managing organization settings can check those instructions.

  1. Check the Code Mode documentation for instructions on enabling it.
  2. If your organization does not want to use it, check the documentation for instructions on disabling it.

Plugin installation checks Claude Code version ranges

Claude Code Update: What Changed in v2.1.323

A plugin's plugin.json file can specify engines["claude-code"], which sets the range of Claude Code versions the plugin supports.

If the current version falls outside that range, Claude Code will not load, install, or update the plugin. For installation and updates, it selects the latest version that meets the specified range.

SituationBehavior in v2.1.323Rule
Loading a pluginDoes not load if the version is outside the rangeengines["claude-code"]
Installation or updateSelects the latest eligible versionSpecified version range

TypeScript hook checks produce warnings by default

claude plugin validate now type-checks a plugin's TypeScript hooks modules. Each issue found during the check appears as a warning.

Plugin developers can run this command to check hooks before release. Add --strict to make validation fail when warnings are present.

  1. Run claude plugin validate in the plugin.
  2. Review any warnings. To make the check strict, use --strict.

A choice menu appears when credits run out

Claude Code Update: What Changed in v2.1.323

If a model requires usage credits and credits are turned off or depleted, Claude Code displays a menu. You can stop the task, switch to usage credits, or upgrade your plan.

If model access is blocked after the Claude Code update, choose what to do next from those options. The menu appears when the model requires credits.

Background sessions stop when authentication details do not match

Version v2.1.323 fixes an issue where sessions using a named Anthropic profile, a shell API key, an auth token, or a workload identity could switch to a different login. When the authentication details do not match, the session now stops and reports the reason.

A session also stops if its profile is missing, has changed, or has been overridden by another setting. After a login is rejected, credentials from the previous account that might have remained are cleared from all sessions on the computer.

FAQ

Can I upload more document formats to the Artifact tool?

Yes. Asset uploads in the Artifact tool now support the .docx format.

Can Claude Desktop report progress during a long-running hook?

While a long-running hook is active, it sends a progress heartbeat every 30 seconds. Once Claude Desktop includes this version, the change helps prevent the host from treating the turn as stopped.

Reopen any sessions that were open during the Claude Code update, then continue your work with the changes in v2.1.323.

댓글