What changed
v2.1.283 adds two new managed settings for enterprise model control (deniedModels, availableModelsMatch: "exact"), a new /doctor prompt-audit command to audit CLAUDE.md files and skills for stale model-specific patterns, OTEL logging of MCP tool content (opt-in), Amazon Bedrock's Mantle endpoint as an upstream provider, multiple performance improvements (startup latency, first-reply latency), and approximately 25 bug fixes across SDK sessions, MCP, plugin management, Vim mode, and platform-specific paths.
TL;DR
A broad housekeeping release with two new enterprise governance settings (deniedModels, availableModelsMatch: "exact"), a prompt-auditing tool, OTEL MCP tracing, and significant startup/latency wins.
Developer signal
(1) deniedModels managed setting (enterprise admins). New in .claude/settings.json under managed.deniedModels: an array of model IDs that are blocked even if availableModels would otherwise allow them. Use this when you want to permit a model family broadly but block a specific version — e.g., allow all claude-* models but block claude-haiku-4-5-20251001 due to a known behavior difference. This is additive to (not a replacement for) the existing availableModels list. (2) availableModelsMatch: "exact" managed setting (enterprise admins). Prevents new model releases from automatically entering the allowed set: when a new Anthropic model ships, it stays blocked until an admin explicitly adds its ID to availableModels. Previously, new models inherited access if they matched a prefix in the allowed list. For regulated environments where every model change needs a formal review cycle, this is the flag you need. (3) /doctor prompt-audit (all users). Run /doctor prompt-audit (or /checkup prompt-audit) to scan your CLAUDE.md files, skills, agents, and commands for patterns known to have been written for older Claude models — things like hardcoded version strings, deprecated tool call formats, or instructions that assume Sonnet 3.x behavior. The audit outputs a list of flagged items with explanations. If you maintain CLAUDE.md files that haven't been reviewed since the Fable/Opus 5.x era, run this first. (4) OTEL MCP tool content (observability). Set OTEL_LOG_TOOL_CONTENT=1 to include MCP tool inputs and outputs in OpenTelemetry span events. Previously, OTEL spans captured tool calls but not their content. Combined with a collector like Honeycomb or Jaeger, this enables request-level tracing of what MCP tools received and returned — useful for debugging multi-step agent workflows where a downstream tool produced unexpected output. (5) Bedrock Mantle endpoint. mantle is now an upstream provider in the Claude apps gateway, pointing at Amazon Bedrock's Mantle endpoint. If your org runs Claude Code through a Bedrock-based gateway, check whether your enterprise Claude Code deployment should route via mantle. (6) Performance wins. First-reply latency improved (pattern-compile step now runs while reply streams). claude -p startup is faster (interactive UI no longer loaded for piped/programmatic use). First-request latency improved through reused preconnected API connections. Expect a noticeable startup-time improvement on claude -p workflows. (7) --system-prompt now accepts both text and -file together. --system-prompt text -system-prompt-file myfile.md is now valid — file content prepends the inline text. Previously these couldn't be combined. (8) Windows PowerShell fix. The Bash tool no longer allows deletion of drive roots and Windows protected system directories — a meaningful safety fix for Windows Claude Code users running agents with broad file permissions.