CLAUDE CODE CLI 2.1.111–114: NATIVE BINARY, STRICTER EGRESS, AUTO MODE POLISH, AND POWERSHELL
Anthropic shipped a dense set of Claude Code CLI updates that tighten security, speed up the tool, and add deeper automation options. Release notes on GitHub c...
Anthropic shipped a dense set of Claude Code CLI updates that tighten security, speed up the tool, and add deeper automation options.
Release notes on GitHub cover 2.1.111 through 2.1.114, headlined by a switch to spawning a native binary, a new sandbox.network.deniedDomains setting, and quality-of-life tweaks like smarter keybindings and fewer permission prompts releases. A rollup from Releasebot highlights Opus 4.7 “xhigh,” Auto mode access for Max subscribers, and new skills like /ultrareview and /less-permission-prompts summary.
Opus 4.7 integration saw bug fixes for Auto mode availability, an interactive /effort slider with the new xhigh tier, and cloud-based multi-agent review via /ultrareview. Windows users get a progressively rolling PowerShell tool toggle, and setup steps for Vertex and Bedrock now report the right settings path when CLAUDE_CONFIG_DIR is set.
The 2.1.114 patch also fixed a crash in the permission dialog when a teammate requested tool permission via agents, rounding out a security- and ergonomics-focused week.
Native binary startup and fewer prompts reduce friction for daily use while giving teams stronger egress control via deniedDomains.
Auto mode and /ultrareview move the CLI closer to dependable autonomous workflows for code review and iterative changes.
-
terminal
Add sandbox.network.deniedDomains and verify it overrides broad allowedDomains wildcards; try blocking telemetry, artifact registries, and known test hosts.
-
terminal
Exercise Auto mode with Opus 4.7 across /effort levels (including xhigh) and compare latency and review quality with /ultrareview on a real PR.
Legacy codebase integration strategies...
- 01.
Upgrade to ≥2.1.114 and confirm the native-binary spawn works in CI/devcontainers; pin per-platform optional dependencies if your images are minimal.
- 02.
Adopt /less-permission-prompts to seed .claude/settings.json and layer deniedDomains on top of existing allowlists; validate with corporate proxies.
Fresh architecture paradigms...
- 01.
Start with a deny-by-default policy: minimal allowlist plus explicit deniedDomains, then enable Auto mode and /ultrareview for PR gates.
- 02.
Choose cloud connectors early (/setup-vertex or /setup-bedrock) and standardize the CLAUDE_CONFIG_DIR location in your dev images.
Get daily CLAUDE-CODE-CLI + SDLC updates.
- Practical tactics you can ship tomorrow
- Tooling, workflows, and architecture notes
- One short email each weekday