Claude Code Now Says Why a Command or Feature Is Turned Off for Your Provider or Sign-In

Claude CodeView original changelog

Claude Code 2.1.326 adds a /status row that says when a provider or an environment variable such as DISABLE_TELEMETRY turns features off. Commands that are unavailable now explain why instead of printing "Unknown command".

Key Takeaways

  • Unavailable commands explain themselves instead of "Unknown command".
  • /status shows when features are off due to provider or env vars.
  • Malformed tool-rule flags warn at startup.
  • Broken JSON settings errors give line and column.
  • Mid-session settings errors now warn instead of being skipped silently.
  • Administrator-added managed-mcp.json now gets an explanatory message.

No more "Unknown command"

Commands that are off for a user's provider, sign-in or an environment variable such as DISABLE_TELEMETRY now say why, instead of reporting "Unknown command". A new row in /status also says when the provider or an environment variable has turned features off.

Related clarity improvements

The release adds a startup warning when an --allowedTools, --disallowedTools or --tools value has an entry that does not look like a complete rule, a message explaining why MCP servers stop loading when an administrator adds managed-mcp.json mid-session, a note in /plugin and claude plugin list when a malformed plugin.json field is ignored, and a line and column in the error for a settings or .mcp.json file with broken JSON. Settings files saved with an error mid-session are no longer skipped silently, and a warning now names the file.