Claude Code v2.1.319 Changes Auto Mode and Adds MCP Task Backgrounding

Claude Code v2.1.319 was published on November 6, 2026, with a change to auto mode that could affect teams running with telemetry or feature flags turned off. In that setup, including behind LLM gateways, calls the server cannot check are now asked about or denied. There is no fallback to the built-in classifier. Users who want to keep the classifier can set CLAUDE_CODE_AUTO_MODE_SERVER=0. Bedrock, Vertex and Foundry are unchanged.

The release also adds several features. When an MCP server runs a tool call as a task, Claude Code now moves it to the background and reports the result to Claude when it finishes. Developers who prefer the old wait behavior can set CLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUND. A new permissions.denyInsteadOfPrompting setting denies any tool call that would wait on a permission prompt, so the turn continues in terminal sessions, subagents and teammates. Other additions include a /claude-api latency-optimize command, a CLAUDE_CODE_DISABLE_FEATURE_FLAGS variable, and several Claude apps gateway updates covering spend reporting, pooled budgets, a sign-in notice, and JSON logs.

Why it matters

The auto mode change can quietly block work in environments that disable telemetry or feature flags, so it is the most important item for administrators. The permission and MCP task changes alter how sessions behave when nobody is watching. Teams that run unattended agents should review these settings before upgrading.

What to do

If you use gateways or disable telemetry, test auto mode after upgrading and set CLAUDE_CODE_AUTO_MODE_SERVER if you need the built-in classifier. Check whether your managed settings need the new permission or MCP task options. Confirm exact behavior and rollout details on Anthropic’s documentation before changing production configurations.