2.1.281 adds assume_role and guardrail to Bedrock upstreams. assume_role swaps long-lived IAM credentials for per-developer STS tokens. guardrail applies a Bedrock guardrail to every request. Both shift the trust boundary in multi-account AWS deployments.
A new internal request tag in 2.1.275 caused 400 errors on every proxy-routed API call. 2.1.276 hotfixed it the same day. Breakdown of the failure, affected configs, and three secondary operator changes worth auditing.
Claude Code 2.1.274 fixes six MCP failure modes that silently break production tool sessions, adds store.connect_timeout_seconds and CLAUDE_CODE_GATEWAY_DRAIN_TIMEOUT_MS to the Claude apps gateway, and makes corrupted transcripts self-heal instead of looping forever.
Claude Code 2.1.273 ships opt-in gateway hint headers exposing request class, agent type, and compaction state to any LLM proxy. It also flips the auto mode classifier to local-only on Bedrock, Vertex AI, and Foundry — only one change has a revert path.
Claude Code 2.1.269 ships with a gateway discovery timeout override, a hard cap on concurrent workflow agents, and a fix for deny rules that were silently applying beyond their config source. Each one changes how operators govern Claude Code at scale.
Since 2.1.265, every turn through a third-party Anthropic-compatible endpoint failed with HTTP 400. Version 2.1.268 fixes it and adds gatewayInternalNetworks CIDR policy, pricing sync to gateway.yaml, and byte-stable prompt caches for Bedrock, Vertex, and Foundry.
Three operator-facing changes land in 2.1.267: a new maxEffortLevel cap across Bedrock, Vertex, and Foundry; a flag to stop prompt-snapshot reuse during iteration; and a marketplace containment bypass fix. Plus twelve prompt-cache stability improvements.
2.1.265 silently broke all gateway and proxy setups that had CLAUDE_CODE_USE_GATEWAY set alongside an API key or custom auth. Here's the exact affected configuration, the error, and what the release adds for gateway operators.
Fable 5.1 prompt caching silently excluded post-tool-result context, re-sending it uncached on every tool-call turn. Claude Code 2.1.260 fixes it — along with cache-miss diagnostics, a Read() permission revert, and a managed CLAUDE.md governance change.
Claude Code 2.1.261 gateway policy telemetry operator changes expose four proxy failure modes: hidden organization policy fetches, malformed client IP parsing, JSON/protobuf OTEL drift, and Bedrock setup checks behind TLS inspection.
Claude Code 2.1.259 ships managedMcpServers for org-wide HTTP/SSE MCP rollout, breaks the allowedMcpServers filter for managed entries, and fixes a concurrent-session bug that was silently corrupting workspace trust and MCP state in multi-agent CI runs.
Claude Code ships Fable 5.1 with 1M context and a hard auto-mode gate on cloud metadata fetches — here is what every operator running production pipelines must audit now.
Claude Code 2.1.251 adds PreModelSwitch and PostModelSwitch hooks that let operators block, confirm, or annotate model switches in real time. Combined with new spend-limit visibility and per-session cache metrics, this release makes the client itself a usable governance surface.
Claude Code 2.1.247 ships a built-in cost-profiling command that walks operators through caching, batch, token hygiene, and model-choice levers, and fixes a silent failure where sub-agents died on their first model call without activating the gateway fallback chain.
Claude Code 2.1.243 adds modelPicker, promptCacheTtl, and modelPricing — three managed settings that let gateway operators lock the model menu, tune cache TTLs per agent tier, and replace list-price cost figures with contracted rates.
Claude Code 2.1.239 started surfacing the 1.1× US-only-inference premium in /cost and status-line estimates for data-residency workspaces. Teams routing through Bedrock or Vertex avoid the surcharge by design — here is what that means for your provider selection.
A stripped Content-Type response header from proxies, API gateways, or load balancers caused Claude Code to re-run every Bedrock turn in non-streaming mode — billing you twice per request. Here is how to verify exposure and what else 2.1.239 fixes for gateway operators.
2.1.238 adds --proxy-authorization-command and --proxy-authorization-file to self-hosted runners, ending static-header workarounds for corporate proxies. It also introduces --defer-shutdown-max-min and extends headersHelper to marketplace catalog fetches.
Claude Code 2.1.237 silently fixed a bug that invalidated prompt caching for every session routed through a custom base URL. If you've been routing Claude Code through a gateway, you've been paying full context-window cost on every turn since at least 2.1.229.
Version 2.1.233 adds forward_user_identity to surface per-developer identity through the apps gateway to any downstream proxy, fixes silent 400/413 swallowing on Vertex, Foundry, and AWS, and closes an infinite-reconnect loop in MCP v2 on serverless hosts.
Claude Code 2.1.229 injects SSE keepalive pings into gateway streaming responses during long thinking pauses, preventing silent idle-timeout disconnects on Vertex AI and Bedrock. Plus: /commit-push-pr now blocks dangerous git flags and the sandbox enforces IPv6 fail-closed.
2.1.228 fixes a settings-merge bug where marketplace entries could silently inherit custom headers from lower-precedence settings tiers, and makes Vertex AI credential failures fast — two changes that change how you audit operator deployments.
Claude Code gateway spend-limit support changes budget enforcement from a late API failure into an operator-controlled warning with cap, reset time, and policy text.
Claude Code 2.1.223 fixes a gateway model discovery bug that was hiding Claude models registered with provider-prefixed IDs, closes four permission bypass paths, and changes how auto-compaction handles 1M-context models.
Three fixes in Claude Code 2.1.222 directly affect operators running custom ANTHROPIC_BASE_URL gateways: stream idle timeout now respects keepalives from any endpoint, a PreToolUse hook bypass in background tasks is closed, and worktree git-command scope is hardened.
2.1.219 ships sandbox.network.strictAllowlist, raises nested subagent depth from 1 to 3, and caps dynamic workflows at medium by default — three changes that alter security posture, cost exposure, and agent orchestration policy without a single code change.
Claude Code misattributed all Bedrock application-inference-profile ARN traffic to the same model ID since February 2026, collapsing Haiku and Opus costs to ~$0.23 per call. Version 2.1.218 fixes ARN resolution — but your historical gateway spend logs are wrong.
Claude Code 2.1.216 closes a worktree subagent git isolation bypass and eliminates quadratic session slowdowns. Here is the operator audit checklist and what the new sandbox.filesystem.disabled setting changes.
Version 2.1.215 removes the automatic execution of /verify and /code-review skills. Teams running CI pipelines or background agents that relied on passive quality gates must now invoke these explicitly or the gates silently vanish.
Version 2.1.214 closes seven permission-check bypass paths in Bash and PowerShell, gates Docker daemon-redirect flags, adds EndConversation to agentic sessions, and ships OTel attributes for gateway-level billing correlation.
Claude Code Artifacts can now pull live data through each viewer's own MCP connectors — not the creator's. That inversion changes how teams build shared internal dashboards, who owns the credential chain, and what your AI gateway must account for.
Version 2.1.212 adds configurable per-session limits on subagent spawns and WebSearch calls, auto-backgrounds long MCP tool calls, and restores prompt caching through custom API gateways and Bedrock/Vertex.
Claude Code 2.1.211 fixes a prompt-caching billing regression that silently billed the trailing system context block as fresh input tokens on every request across Bedrock, Vertex AI, Mantle, and Foundry. Gateway operators have overcharges to investigate.
CVE-2026-55607 is a high-severity Claude Code vulnerability in which a malicious repository could steer the coding agent into unsandboxed code execution. Patched in 2.1.163, it changes how operators should version-pin and audit Claude Code in shared gateway environments.
Claude Code 2.1.207 removes the CLAUDE_CODE_ENABLE_AUTO_MODE opt-in requirement on Bedrock, Vertex AI, and Foundry. Auto mode is now on by default for all managed-provider sessions — operators must add disableAutoMode to maintain prior behavior.
Claude Code origin story routing turns Anthropic's official history into an operator checklist for terminal agents, permissions, context, and parallel swarms.
Claude Code 2.1.203 fixes a critical background-agent bug that silently dropped ANTHROPIC_BASE_URL, sending API keys to Anthropic's default endpoint and failing with 401. Any team routing Claude Code through a custom AI gateway must audit and upgrade.
Microsoft Research's peer-reviewed study of tens of thousands of engineers is the first field evidence of coding agent ROI — and the governance gap that forced token spend limits. The operator checklist every team needs before scaling Claude Code or any CLI agent.
Claude Code security review routing moves from demo to government scale as Alberta scans 466M lines, runs 50 agents, and keeps human approval in the loop.
Claude Code 2.1.202 adds workflow.run_id and workflow.name OTel attributes plus a dynamic workflow size setting — two changes that finally give operators observability and budget control over multi-agent orchestration runs.
Claude Code 2.1.200 renames the default permission mode to "Manual" and removes auto-continue from AskUserQuestion dialogs — two changes that will stall CI pipelines and background agent workflows without an explicit config update.
Claude Code 2.1.199 fixes five operator-critical issues: TLS proxy errors fail fast with guidance, subagent silent successes become real errors, retry watchdog jumps to 300, a Linux daemon kill-loop is patched, and SendMessage guards against name mismatch.
Claude Code 2.1.198 adds the Claude Platform on AWS as a native gateway upstream, advances the failover chain on model-not-found errors, and auto-refreshes AWS STS tokens — three changes that directly affect how routing teams configure provider fallback.
Anthropic's new Enterprise model entitlements let admins lock specific Claude models to roles and cap the effort level—directly capping token spend—per role. Here is what AI engineering teams need to configure.
Three operator-relevant changes in v2.1.196 reshape how you govern model selection, stream reliability, and custom-endpoint security for Claude Code deployments.
Claude Code plugin governance routing in v2.1.195 fixes plugin consent, hook exact-match behavior, and background-agent durability for coding-agent fleets.
Claude Code shell classifier routing in v2.1.193 adds classifyAllShell and assistant-response OTEL, forcing operators to audit command policy and telemetry privacy.
Claude Code MCP reliability routing gets a practical v2.1.191 upgrade: retries, headless OAuth, durable settings refresh, and sandbox host memory now belong in operator policy.
2.1.187 changelog: sandbox.credentials setting stops sandboxed commands from reaching credential files and secret env vars; org model restrictions now enforced at picker, --model flag, /model command, and ANTHROPIC_MODEL — with a visible restriction message.
Anthropic's Claude Tag on Slack introduces channel-scoped agent identities with per-channel tool access and org-level token spend controls — the same governance primitives AI engineering teams need for any multi-agent deployment.
Claude Code 2.1.186 changes two defaults that affect every operator: bash commands now auto-trigger agent responses, and background subagents surface permission prompts instead of auto-denying. Here is what to audit before updating.
Claude Code 2.1.185 reclassifies webhook and scheduled-task deliveries as task notifications, blocking them from approving pending actions in auto mode. Operators running CI/CD webhook pipelines and MCP-authenticated gateways need to review their automation boundaries.
Claude Code 2.1.181 introduces /config key=value syntax for changing any setting mid-conversation—no JSON files, no restarts. For teams routing Claude through a gateway, this changes how model selection, thinking mode, and managed settings are enforced at runtime.
Claude Code 2.1.183 tightens auto mode safety by blocking destructive git and infrastructure commands unless explicitly requested, closes a webhook trigger approval bypass, and fixes MCP auth stub exposure in headless mode.
Anthropic’s 400K Claude Code sessions show domain expertise doubles verified success and drives 5× output. Use the data for token budgets, model tiers, prompt caching, and governance.
Claude Code 2.1.181 fixes a silent prompt-caching regression that was inflating costs for every team running a custom ANTHROPIC_BASE_URL or Microsoft Foundry endpoint. It also enforces the five-level subagent depth cap for foreground agents.
Claude Code 2.1.181 rewrites the cross-session agent peer trust model from 'treat with suspicion' to 'collaborative teammate.' Peer agents can now act on requests without per-action skepticism — but escalation paths and permission laundering remain hard-blocked.
Claude Code 2.1.179 patches three silent failure modes that specifically affect teams routing through a custom API gateway: a 401 auth regression in claude agents workers, compaction ignoring the configured fallback model, and mid-stream response loss on connection drops.
Claude Code 2.1.178 ships Tool(param:value) permission grammar — letting operators write rules like Agent(model:opus) to block Opus subagents — plus nested .claude/ directory scoping and a pre-flight auto-mode classifier that screens subagent spawns before they run.
Anthropic's Agent SDK billing split is live as of June 15. The new per-user monthly credit ($20–$200 by plan) draws from a separate meter — but the ceiling changes the routing decision for every production agent team.
DeepSeek's official awesome-deepseek-agent docs show the Claude Code ANTHROPIC_BASE_URL setup, Anthropic-compatible API path, V4 Pro/Flash model IDs, and OpenCode/Copilot integration notes for coding-agent routing.
Claude Code v2.1.175 adds enforceAvailableModels, a managed setting that constrains the Default model to your availableModels allowlist and prevents project or user settings from widening it — closing a silent governance gap for enterprise teams.
The June 12 Claude Code release adds per-skill, per-agent, and per-MCP-server cost attribution to the VSCode /usage dialog, fixes a Bedrock GovCloud bug, and closes a background-session credential leak.
Claude Code's June 8 release adds --safe-mode, fixes slow claude -p / --print runs on Windows, hardens managed settings MCP policy enforcement, and restores a 5-minute Vertex / Foundry idle timeout.
Claude Code v2.1.166 upgrades fallbackModel to support up to three ordered fallback models for overload resilience, extends it to interactive sessions, and hardens multi-agent trust: relayed SendMessage calls no longer carry user authority.
Step-by-step Claude Code workload identity federation setup: connect an OIDC issuer, create Anthropic service accounts and federation rules, then replace static sk-ant keys in CI/CD, gateways, and agent runtimes with short-lived tokens.
Claude Code now refuses to launch when its version falls outside an operator-defined range. requiredMinimumVersion and requiredMaximumVersion managed settings let teams lock their entire dev fleet to approved Claude Code builds — no voluntary upgrades, no accidental drift.
Claude Code auto mode now runs on AWS Bedrock, Google Vertex AI, and Microsoft Foundry — set CLAUDE_CODE_ENABLE_AUTO_MODE=1 and your coding agent runs inside your VPC. Here's what changes for billing, latency, and fallback routing when you switch from the Anthropic API.
Claude Code MCP timeout and WebFetch policy changed in the June 3 release: explicit WebFetch deny rules now beat preapproved hosts, while sub-1000 ms MCP timeout values fall back to MCP_TOOL_TIMEOUT/default instead of tripping the watchdog.
The June 2 Claude Code release propagates OTEL_RESOURCE_ATTRIBUTES as labels on every metric datapoint, enabling per-team cost allocation at the Prometheus level without gateway-side custom instrumentation.
Claude Code's June 2 release adds interactive prompts before writing shell startup files and build-tool configs in acceptEdits mode — a change that can silently break unattended CI pipelines that rely on auto-merging AI-generated configuration changes.
Claude Code v2.1.157 introduces agent dispatch routing via settings.json, auto-loaded .claude/skills plugins, and OTEL tool-parameter telemetry—three operator controls for governed multi-agent coding pipelines.
Claude Code's May 28 patch fixed an OAuth credential regression that could send user Anthropic tokens to custom API gateways. Here is the gateway audit checklist for token isolation, logging, and subagent MCP policy enforcement.
Claude Code's --fallback-model can now auto-switch after model-not-found errors. Here's how teams using an API router should separate client fallback, gateway fallback, OTEL entrypoint metrics, and plugin governance.
Anthropic official Claude Code best practices guide (code.claude.com): context management and context engineering are first-class constraints for routing teams. Context windows fill fast, performance degrades as they fill, coding agents burn tokens 3-10× vs chat.
How to use DeepSeek Anthropic API at api.deepseek.com/anthropic with Claude Code and the Anthropic SDK — plus the routing hazards around unsupported fields, cache_control, MCP tools, and silent fallback to deepseek-v4-flash.
DeepSeek's official integration guide for Claude Code, OpenCode, and OpenClaw — API setup, per-tier V4 model routing, and Anthropic-compatible endpoint configuration for coding agents.
DeepSeek API model names changed 2026: deepseek-chat becomes deepseek-v4-flash and deepseek-reasoner merges into deepseek-v4-flash (thinking mode) or deepseek-v4-pro (1M context). Deprecated July 24, 2026. New Anthropic-compatible endpoint at /anthropic for Claude Code routing.
Anthropic doubled Claude Code rate limits and raised Opus API ceilings with 220K GPUs at SpaceX Colossus 1. Learn how this changes fallback triggers, scheduling, and multi-provider routing strategy.
