Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.305entry #6

Claude Code v2.1.305 ·

! shell commands get their own path in SDK input and are refused in the cloud-session view

Bash-mode ! input now travels with inputMode and clientBashCommandCwd in SDK input, and is refused with a message in a remote cloud-session view

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

Unclear It is not clear which clients send shell command input this way or whether you can use it.

What

In Claude Code, typing ! before a line runs it as a shell command (bash mode) instead of sending it to Claude. This release changes how that input is handled in two places.

  • SDK and headless input: the SDK is the programming interface for driving Claude Code from other programs, and headless means running without the interactive screen. Input with inputMode === "bash" is now handled separately. It skips prompt-submit hooks (your own scripts that normally run when a prompt is sent), uses different replay and acknowledgement handling, and accepts clientBashCommand and clientBashCommandCwd parameters.
  • Submitted payload: inputMode and clientBashCommandCwd are added to what is sent, set only for client bash commands.
  • Remote view: when the session is remote and the input is in bash mode, the terminal interface refuses to send it and shows "'!' commands can't be sent to a cloud session from this view; open the session to try it there". Before, nothing stopped it.

Why

If you type !cmd while looking at a cloud session, you now get a clear refusal and a pointer to where it will work, instead of the command failing quietly or going somewhere unexpected.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which clients send shell command input this way or whether you can use it.

See this entry in the whole of v2.1.305 →

Feedback