Claude Code /status Now Lists Broken Config Files and /config Shows When Another Setting Overrides a Row

Claude CodeView original changelog

Claude Code 2.1.327 turns /status into a place to find out why something is not working. It now lists broken agent, skill, command and output style files, keybinding errors, an unavailable sandbox, ignored permission settings and hook matchers that never match. /config adds a note when other settings override a row.

Key Takeaways

  • /status now lists silent configuration failures in one place, including broken agent, skill, command and output style files.
  • Keybinding errors and an unavailable sandbox are reported there too.
  • Ignored permission settings and hook matchers that never match are surfaced, which are the usual reasons a rule seems to do nothing.
  • /config notes when another setting overrides a row, explaining why a change has no effect.
  • A failed settings save from /config now prints a line under the prompt instead of failing silently.
  • Together these changes cut the guesswork when debugging a Claude Code setup.

A diagnostic list inside /status

Claude Code 2.1.327 adds a list to /status of configuration problems that usually fail quietly. It names broken agent, skill, command and output style files, keybinding errors, a sandbox that is unavailable, permission settings that are ignored and hook matchers that never match anything.

These are the failures users typically discover only because a skill never fires or a hook never runs. Having them in one command shortens the path from "this does nothing" to "this file is malformed" without reading logs or guessing.

/config explains overridden rows

/config now shows a note when other settings override a row. A user who changes a value and sees no effect can now see that a higher-priority setting, such as a managed or project one, is winning, rather than assuming the change failed to save.

A related fix makes failures to save a settings change from /config and similar commands visible: a line under the prompt now says so, where before there was no warning.