[Bug] `/status` command Config output does not match documentation regarding configuration layers and settings display (re-opening)

Open 💬 2 comments Opened Jun 12, 2026 by gene1wood

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

(Originally opened in #59214 but nobody responded in 2 weeks so the GitHub bot closed it)

The Claude documentation at https://code.claude.com/docs/en/settings says

Run /status inside Claude Code to see which settings sources are active. The Status tab includes a Setting sources line that lists each layer Claude Code loaded for the current session, such as User settings or Project local settings. When managed settings are in effect, the entry shows the delivery channel in parentheses, for example Enterprise managed settings (remote), (plist), (HKLM), (HKCU), or (file). A layer appears in the list only when that source is loaded with at least one key, so an empty list means no settings sources were found. The Setting sources line confirms which sources are being read. It does not show which layer supplied each individual key. The Config tab in the same dialog is an editor for a fixed set of toggles such as theme and verbose output, not a view of your settings.json contents. If a settings file contains errors, such as invalid JSON or a value that fails validation, Claude Code shows a setup issues notice at startup and /status lists the affected files. Run /doctor to see the details for each error.

This is not the behavior of the "/status" command. The "/status" command shows 4 menus, one of which is "Config". The "Config" menu just shows a list of settings and their values, nothing like what the documentation describes.

For example, it does not show each configuration layer or it's origin.

Also, the list of settings shown in the "Config" tab of "/status" doesn't actually contain the settings. If, for example, the settings.json file contains this section

{
  "hooks": {
    "Notification": [
      {
        "hooks": [{ "type": "command", "command": "uname" }]
      }
    ]
  }
}

the "/status" commmand shows nothing about "hooks" or "Notification". The nearest thing is a line that says "Local notifications Auto" which is unrelated.

What Should Happen?

The documentation should describe how the feature works.

Error Messages/Logs

Steps to Reproduce

  1. Read the documentation page linked above
  2. Run the /status command
  3. See how the documentation and feature behavior differ

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.174

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗