Anthropic released Claude Code 2.1.319 on 6 November 2026. Most of the release notes are routine, but three items say something about how AI coding tools are being used: more and more of them are running without a person watching.
What the changelog says
permissions.denyInsteadOfPromptingis a new setting. A tool call that would otherwise stop and wait for a human to approve it is denied instead, so the run carries on.- MCP tasks: when a connected tool server runs a call as a task, Claude Code now moves it to the background and reports back when it finishes. A setting,
CLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUND, switches this off. - Auto mode: where telemetry or feature flags are off, including behind company LLM gateways, calls the server can’t check are now asked about or denied rather than waved through by the built-in classifier.
- The release also lists 90 bug fixes and a new
/claude-api latency-optimizecommand.
The interpretation
A prompt that waits for approval is fine when a developer is at the keyboard. It is a problem when the agent is running on a schedule or in a pipeline overnight, because the job simply hangs. The new setting resolves that in the cautious direction: unapproved actions are refused, not silently allowed.
That is the useful signal for buyers. The tooling is moving from “assistant beside a developer” to “agent running on its own”, and the safety defaults are being tuned for that. The auto-mode change points the same way: when the tool can’t verify a call, it should ask or refuse.
So what
If a supplier says AI agents work on your codebase, ask what those agents are allowed to do when nobody is watching, and what happens when they hit something they aren’t permitted to do. A good answer names explicit permissions, a deny-by-default stance and a human review before anything ships. BuildApps runs AI workflows with defined permissions and human review. See AI-assisted development, custom software development, or start a project.