---
title: 'In the News: November 6, 2026 (Extra 2)'
description: 'Claude Code 2.1.319 stops falling back to the built-in classifier for auto mode behind gateways, and adds a setting that denies tool calls instead of waiting on a prompt.'
canonical_url: 'https://darkfactory.dev/news/2026-11-06-extra-2'
markdown_url: 'https://darkfactory.dev/news/2026-11-06-extra-2.md'
collection: news
date_published: '2026-11-06T16:20:00-05:00'
date_modified: '2026-11-06T16:20:00-05:00'
---

# In the News: November 6, 2026 (Extra 2)


Claude Code 2.1.319 changes what unattended runs do when nothing can approve an action. Auto mode behind a gateway no longer falls back to a local classifier, and a new setting makes a blocked tool call fail and carry on instead of waiting for a person.

## 1. Claude Code 2.1.319 makes unattended runs deny actions they cannot check

**[Claude Code v2.1.319 release notes](https://github.com/anthropics/claude-code/releases/tag/v2.1.319)** · Anthropic · GitHub release, November 6, 2026

The release notes say that with telemetry or feature flags off, including behind LLM gateways, auto mode now asks about or denies calls the server cannot check. It no longer falls back to the built-in classifier. Setting `CLAUDE_CODE_AUTO_MODE_SERVER=0` keeps the old behaviour, and Bedrock, Vertex and Foundry are unchanged. A related fix says `claude -p` used to exit 0 in auto mode when its actions were refused for lack of a safety check; text and JSON output now exit 1.

The same release adds `permissions.denyInsteadOfPrompting`. A tool call that would wait on a permission prompt is denied and the turn continues, in terminal sessions, subagents and teammates. It also moves MCP tool calls that run as tasks into the background right away and reports the result when they finish; `CLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUND` turns that off. Another fix says Bash deny and ask rules had missed commands written with quoted words.

**Why it matters:** Anyone running Claude Code headless or through a gateway should check what their harness now does when the safety check is unreachable: a nonzero exit on a refused action will show up in scripts that assumed success. The release notes describe the changes; they do not say how many setups relied on the old fallback.