Skip to content
BENIBIX Learn

claude doctor vs /doctor

People think claude doctor and /doctor are the same check typed in two places, and they are not. claude doctor runs in your shell with no session open. It only reads, so it is the one to use when Claude Code will not start. /doctor runs inside a session. It checks more, and it offers to fix what it finds once you say yes.

AI⌨️ Claude Code

claude doctor Command

It checks your install from the shell and changes nothing.

claude doctor checks your Claude Code install from the shell, with no session. It prints how well the install is doing, any settings file with a mistake in it, and if this computer can use Remote Control. It only reads, and changes nothing. Use it when Claude Code will not start. Inside a session, /doctor does a checkup that also offers fixes.

Example
Claude Code quits as soon as Jack opens it. He runs claude doctor, which shows a broken line in his settings file. He fixes the line, and it starts.
Why it matters
When the program itself will not open, you cannot type /doctor. This still works.
Full entry
AI⌨️ Claude Code

/doctor Command

It checks your setup and offers to fix what is wrong.

/doctor is a bundled skill that runs a checkup on your Claude Code setup. It looks at the install, the settings files, your extensions and your CLAUDE.md. It flags things like a broken settings file, an extension you never use, or CLAUDE.md lines Claude could learn from the code. Then it proposes fixes and applies them only after you agree. If Claude Code will not start at all, run claude doctor in your shell instead.

Example
Jack's hooks stopped running. /doctor finds that one settings file is broken, shows the bad line, and fixes it once he says yes.
Why it matters
When something does not load, you get a list of causes. You do not spend the day guessing.
Full entry

In one line

claude doctor Command
It checks your install from the shell and changes nothing.
/doctor Command
It checks your setup and offers to fix what is wrong.