Claude Code 2.1.326 Adds Startup Warnings

By Rogier Muller11.17.26
Claude Code 2.1.326 Adds Startup Warnings

2.1.326 adds Ctrl+O for hidden startup notices in @anthropic’s Claude Code, and that small change matches the shape of the release: more of the session’s hidden state is now visible before a developer starts debugging the wrong thing. The release also changes Code Mode with agent teams and explains more clearly what happens when managed MCP configuration appears during a live session. For anyone searching for Claude Code MCP behavior, the important bit is direct: when an administrator adds managed-mcp.json during a session, Claude Code now says why MCP servers stop loading, and open sessions still need a restart for the configuration to apply in full.

See session state before chasing the task

The changelog entry adds a startup warning when --allowedTools, --disallowedTools, or --tools contains a value that does not look like a complete rule. That is a good warning to have near the start of the session, because tool boundaries are easy to misread once the agent is already mid-task.

It also adds a row to /status when a provider or an environment variable such as DISABLE_TELEMETRY turns features off. That matters in ordinary debugging. A session can look broken when it is actually following a provider setting or an environment flag.

For repos with shared Team conventions, the mode a session starts in becomes part of the operating context. Startup notices, /status, and visible failure hints make that context easier to inspect instead of guessing from later behavior.

Rolling this out in your team?

We train engineering teams on their own codebase in two days. Claude Code setup, shared rules and review included.

Code Mode now follows agent teams

The release adds support for turning on Code Mode while agent teams are enabled. If Code Mode was already turned on, sessions with teams enabled now start in Code Mode.

That connects this release to the earlier Code Mode work in Claude Code 2.1.323 Adds Code Mode. The current change closes a practical gap: a session using agent teams no longer has to treat Code Mode as a separate manual step when it is already configured.

There are also default-mode changes. Terminal and VS Code sessions in organizations using the Claude Code + Cowork HIPAA configuration now start in auto mode by default, with disableAutoMode available to turn that off. Terminal and VS Code sessions with no mode set also start in auto mode when the organization policy has not loaded.

Managed MCP now explains the interruption

The MCP change is narrow and useful. Claude Code now adds a message explaining why MCP servers stop loading when an administrator adds managed-mcp.json during a session.

The changelog also says a managed-mcp.json added mid-session may apply at the next check. That is a partial behavior. Restart open sessions when the managed MCP file needs to apply fully.

This is the practical edge of Claude Code MCP work: the integration layer can be correct on disk while a running session still needs a clean start. A visible explanation helps separate a configuration event from a broken server.

Try one repo before changing habits

Use one existing repo and run a short check before changing shared instructions or permissions. This belongs to the Review step in our methodology: collect evidence from the tool’s current state before deciding that the prompt, repo rules, or integration is wrong.

What to check How to check it What you learn
Code Mode with agent teams Start a session with agent teams enabled where Code Mode is configured Whether the session begins in the intended mode
Managed MCP behavior Change managed-mcp.json only in a controlled session Whether Claude Code explains stopped MCP loading and whether a restart is needed
Startup and feature state Press Ctrl+O, then run /status Whether hidden notices, provider settings, or environment flags explain the session behavior

Keep this small. The point is to verify the release behavior in a real repo without mixing it with prompt rewrites, plugin changes, or new MCP servers.

Limits worth respecting

Some changes in 2.1.326 improve visibility without promising instant application. Managed MCP configuration added during a session may apply at the next check, but the changelog still says to restart open sessions for it to apply in full.

The OpenTelemetry change is also opt-in. OTEL_RESOURCE_INCLUDE_HOST can include host.name and host.id in resource attributes, and it is off by default.

Plugin handling gets more explicit too. /plugin and claude plugin list now note when malformed plugin.json fields such as author or homepage are ignored. That is a quiet but useful distinction: Claude Code can keep going while telling you which metadata it skipped.

Further reading

What to do next

Start from Team conventions.

Train your team on Claude Code

Two days on your team's own repository, onsite or remote, with a written proposal before you commit.

Book a call

Prefer to measure first? Take the free team check.