Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

plugin.command.run character-limit check silently removed

Plugin command.run no longer rejects overly long arguments, only logs their length

You'll notice Improvements
JSON All of v2.1.275
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Plugin APIArea: what it touches
ImprovementsKind: in v2.1.275,
ImprovementsSection of the release
What

The check that runs before a plugin's command.run operation executes used to reject the call with an error if its arguments exceeded a maximum length. That rejection has been removed: the check now only records the argument length for telemetry (internal usage tracking) and always allows the call to proceed.

Why

Plugin commands with very long arguments that would previously have been blocked can now run instead, since the length limit is no longer enforced, only measured.

Read from
Names in the bundlecommand.run
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up command.run, on Troubleshoot a mod. ### `no command.run hook answered it` plugins/mods/troubleshoot see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up command.run, on Troubleshoot a mod.

See this entry in the whole of v2.1.275 →

Feedback