---
title: "Claude Code v2.1.326: Auto Mode Becomes the Fallback, and Credentials Files Get a Guard"
date: 2026-11-17
tags: ["claude-code","auto-mode","permissions","sandbox","plugins","mcp","changelog"]
categories: ["AI Tools"]
summary: "Claude Code v2.1.326 (Nov 16) lets Code Mode run alongside agent teams, starts sessions in auto mode when no mode is set and organization policy hasn't loaded, and blocks file tools from writing to sign-in files like .credentials.json. Based on the official changelog only; I have not run this version."
---


Version 2.1.326 shipped on November 16. This post relies only on the [official Claude Code changelog](https://code.claude.com/docs/en/changelog). I haven't run this version, and the changelog page is enormous (over a million characters). I read only the top of it, so treat this as a summary of the release notes, not a field test.

## Auto mode as the default when policy is missing

The change with the most operational weight: terminal and VS Code sessions with no mode set now start in **auto mode** when your organization's policy hasn't loaded. Organizations using the Claude Code + Cowork HIPAA configuration also start in auto mode by default. The `disableAutoMode` setting turns this off.

Two readings are possible, and the notes don't settle which is intended:

- Auto mode is now treated as the sensible baseline for autonomous work, which fits the direction of the product.
- A session that fails to fetch managed policy now lands in a *more* autonomous state, not a more restrictive one.

If you manage a fleet, the second reading is the one to test. Set `disableAutoMode` explicitly in managed settings rather than relying on policy delivery being reliable.

## Tighter permission and sandbox checks

The release says many Bash, PowerShell, and file-tool checks now ask for approval or refuse more often. Specifics listed:

- Sandboxed commands on macOS, Linux, and WSL can no longer write to some sensitive home folders by default.
- File tools refuse to write to Claude Code's own sign-in files, such as `.credentials.json`.
- Hooks returning `"decision": "block"` now hold in more cases.

That last item matters for anyone who builds guardrails on hooks. A block decision that used to be bypassable in edge cases is a hole in your spec of what the agent may do. After upgrading, re-run whatever tests you have for your blocking hooks.

This continues the pattern from [v2.1.323–325](/posts/claude-code-v2-1-323-325-code-mode-sandbox-permission-flow/): each release moves more actions back into the approval flow. Expect more prompts in unattended jobs, and budget for that.

## Code Mode meets agent teams

You can now enable Code Mode while agent teams are on. Sessions that already had teams enabled start in Code Mode if you had turned it on. Code Mode is still the experimental feature from the previous releases, so I'd try it on a throwaway branch first.

## Plugins and MCP housekeeping

- Plugin uninstall now also deletes files extracted from MCP bundles (`.mcpb`, `.dxt`), unless another plugin uses them. Fewer orphaned artifacts.
- A `managed-mcp.json` added mid-session may apply at the next check; restarting open sessions applies it in full.
- `/plugin` uninstall, remove, and switch prompts now use arrow keys and Enter. The `y`, `n`, and `u` shortcuts no longer answer them, which will break muscle memory and any scripted keystrokes.

## Performance and fixes

Idle sessions wake the machine less often, typing and resizing are more responsive, and response time after file reads and edits improves, especially on Windows. The release lists 233 bug fixes, including resumed sessions losing turns, `/rewind` behavior, and several sign-in and MCP problems. I can't verify that count beyond the changelog.

## What to do

1. Pin `disableAutoMode` in managed settings if you don't want the fallback.
2. Re-test hook-based blockers.
3. Check CI jobs that drive `/plugin` prompts with keystrokes.
4. Expect more approval prompts from sandboxed Bash.

The direction is consistent: Anthropic keeps tightening the boundary around what an autonomous session can touch, while making autonomy the default posture. That's the right tension for a terminal-native agent, and it's the reason a spec of allowed actions belongs in version control next to your code.

## Sources

- [Claude Code changelog](https://code.claude.com/docs/en/changelog)

