clauding.de
DE

Claude Code

Claude Code 2.1.271: fast mode in remote sessions, and per-command domains for Bash

3 min read AI-generated

A plugin update can now be approved by SHA-256 instead of by yes. Four of the new switches change permissions, not features.

Featured image for "Claude Code 2.1.271: fast mode in remote sessions, and per-command domains for Bash"

Two versions in two days. 2.1.271 landed on Sunday with a list that goes on forever, 2.1.272 on Monday with a single line: «Bug fixes and reliability improvements». I wrote about 2.1.270 two days ago, the hotfix release. This is the backlog it was holding up.

Fast mode reaches remote sessions

Claude Code Remote now knows fast mode, in the cloud and on self-hosted runners. Either the session picks up the host’s setting, or you type /fast into it. Whether it works at all is your organization’s call.

Five fast-mode bugs got cleaned up around it. /fast off used to answer «Fast mode unavailable» instead of turning the mode off. Sessions running with CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK kept re-sending fast requests every turn after the API had already refused. And under the retry watchdog, hitting a usage-credits limit in fast mode failed the turn instead of dropping back to standard speed.

Permissions, not features

Four of the additions don’t change what Claude Code can do. They change who is allowed to do what:

  • Per-command allowed_domains. In auto mode with sandboxing, the hosts a command needs are reviewed together with the command and opened for it alone. Everything else is refused.
  • omitClaudeMd in agent frontmatter and in --agents JSON. Custom and plugin subagents run without your CLAUDE.md files. Managed policy files still load.
  • --accept-command <sha256> on claude plugin install and claude plugin update. You approve exactly the command a previous --json run showed you, instead of waving -y at it.
  • A multiplier above 1, up to 10, in the modelPricing managed setting and in the gateway’s pricing block. Meant for marked-up internal chargeback rates.

Then half a dozen fixes to the Bash permission checker. It was missing the file that fmt or column reads when an option it doesn’t recognise comes first. It skipped files a wildcard expands to. And commands with two directory changes, or a cd-plus-git chain, slipped past the prompt under permissions.blockReadsOutsideWorkingDirectories.

Mouse, artifacts, spinner

The fullscreen /config panel now takes mouse input: the wheel scrolls the settings list, a click on a value changes it, the row under the pointer lights up. An org policy that finishes loading after startup updates the tool and command lists right away instead of waiting for the hourly check. Markdown files published as artifacts render as styled document pages rather than raw text. A session can watch ten artifacts instead of five. And after 45 seconds the spinner says «deep in thought».

The real work here is in the permissions

If you came for features, this release is thin. The direction is the interesting part: sandboxing with per-command domain approval, subagents without inherited instruction files, plugin updates keyed to a checksum. Three answers to one question, which is what an agent may do while you are not watching it.

Working alone in a terminal, you’ll barely notice. If Claude Code runs in your CI, or several people on your team pull the same plugins, this is the week’s actual news.

Sources:

Claude CodeReleaseSecurityMCP