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.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 shell classifier routing in v2.1.193 adds classifyAllShell and assistant-response OTEL, forcing operators to audit command policy and telemetry privacy.
Datadog's 2026 State of AI Engineering report finds that over 70% of organizations run three or more AI models in production. The data reveals what makes multi-model AI routing production-ready — and where teams are still flying blind.
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.
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 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.
Codex eval infrastructure separates a working agent from a self-improving one. OpenAI's Tax AI converted production traces into eval targets and ran Codex-driven iterations automatically. The architecture applies to any team building agents on an API gateway.
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.
