/doctor now waits for organization policy limits to finish loading, via waitForPolicyLimitsToLoad bounded by POLICY_LIMITS_FIRST_ATTEMPT_WAIT_MS, before reporting them. The output gains an 'Organization policy: …' status line that updates once the check resolves, instead of doctor only surfacing settings and env-var issues immediately.
Names in the bundle/doctor
/doctor
Claude Code changelog modified, high confidence
* Fixed managed `skillOverrides` entries keyed on a bundled skill's alias (e.g. `checkup` for `/doctor`) not applying, and `Skill(name)` deny rules not covering a nested skill listed as `<dir>:name`see the edit
claude doctor
Error reference modified, high confidence
Claude Code refuses to start even when another admin source delivers a valid policy. You see this error in interactive sessions, `claude -p`, Agent SDK sessions, [background sessions](/docs/en/agent-view), and most subcommands, `claude doc…see the edit
claude doctor
Deploy managed settings modified, high confidence
* A malformed value in the user-writable HKCU registry key never blocks launch. Claude Code reports it as a notice in `/status` and `claude doctor` instead.see the edit
claude doctor
Claude Code changelog modified, high confidence
* Added an "Organization policy" line to `/status` and `claude doctor` that says why your organization's policy could not be loaded, such as a proxy not passing the endpoint throughsee the edit
/doctor
Extend Claude with skills modified, high confidence
Run `/doctor` for an estimate of the listing's context cost and its biggest contributors. To find skills worth turning off, run [`/skill-doctor`](#find-unused-skills). When the listing exceeds its budget, Claude Code also writes a warning …see the edit
claude doctor
Error reference modified, high confidence
A [permission rule](/docs/en/permissions#permission-rule-syntax) in one of your settings files doesn't have the shape `Tool` or `Tool(content)`, for example because text follows the closing parenthesis or one of the parentheses is missing.…see the edit
claude doctor
Continue local sessions from any device with Remote Control modified, high confidence
* **The organization policy didn't load on this machine**: run `claude doctor` and read the `Organization policy` line. If the line shows the policy isn't loaded, that is what's keeping Remote Control off. Before v2.1.261, `claude doctor` …see the edit
claude doctor
Deploy managed settings modified, medium confidence
To check whether these organization settings reached a given machine, run `claude doctor` there and read the `Organization policy` line, which says where Claude Code loaded the policy from or why it didn't load. Requires Claude Code v2.1.2…see the edit
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on How Claude remembers your project touched a line naming /doctor after this was published.
To have Claude check these files for outdated or conflicting instructions, run `/doctor prompt-audit` in a session. Claude reads your CLAUDE.md, CLAUDE.local.md, and AGENTS.md files, plus the rules, skills, commands, subagents, and output …memory see the edit
Confirmed since
Anthropic's documentation has since written up /doctor, on CLI reference.
| `claude doctor` | Print read-only installation and settings diagnostics from the terminal without starting a session, including install health, settings-file validation errors, and Remote Control eligibility. For the in-session setup che…cli-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
/doctor on Claude Code changelog