Claude Code v2.1.319 adjusts auto mode gateway behavior
Understand this story
Anthropic released Claude Code v2.1.319, adjusting how auto mode behaves when telemetry is disabled or when running behind an LLM gateway: calls that the server cannot verify are now prompted or rejected instead of falling back to the built-in classifier. Setting CLAUDE_CODE_AUTO_MODE_SERVER=0 preserves the previous behavior; Bedrock, Vertex, and Foundry are unaffected. The release also introduces backgrounding of MCP tasks, which can be disabled with CLAUDE_CODE_DISABLE_MCP_TASKS=1; setting CLAUDE_CODE_LOOP_KEEPALIVE=1 preserves the old behavior. Setting CLAUDE_CODE_AUTO_MODE_SERVER=1 enables server-side verification even when CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS is on; if the latter is enabled via managed settings, the former must also be set.
AI overview based on source reports · Updated 2 hr ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Claude Code Releasesv2.1.319
Claude Code v2.1.319 changes auto mode so calls the server can't check are asked about or denied when telemetry or feature flags are off, adds MCP task backgrounding in the terminal with a CLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUND opt-out, and introduces a permissions.denyInsteadOfPrompting setting. It also adds /claude-api latency-optimize, spend breakdowns in /usage, several Claude apps gateway admin settings, and a long list of fixes spanning MCP, /diff, permissions, sandboxing, self-hosted runners, VSCode and cloud sessions.
Activity for this story
Not enough continuous observations to show a trend yet.