When Integrations Suddenly Break, Self-Diagnose with /doctor and Fix It with f

After updating, have you ever found IDE integration suddenly not working, or something that was fine acting strange? When you do not know the cause, you end up wandering through config files for a long time. At such times, instead of wandering, the first command to run is /doctor. It checks the installation and config state on its own, and if there is a problem, it fixes it right there.

Definition

/doctor is a command that diagnoses Claude Code's installation and config state. Just like the name, it is a "doctor." It shows at a glance what is healthy and what is a problem, and fixes detected problems automatically with a single f key.

When something seems off but you do not know the cause, think of it as a tool to get diagnosed first, instead of touching settings by guesswork.

How to Use (by difficulty)

Basics — Diagnosing

Type just this into the chat box.

/doctor

Once you enter it, the check results appear on screen item by item. Healthy items and problem items are marked with icons (checks, warnings, etc.), so you can see at a glance what is wrong.

Advanced — Auto-Fixing

/doctor 실행 → 결과 화면에서 f 키

If a problem shows in the diagnosis result, press the f key on that screen. Then Claude fixes the detected problem on its own. Without needing to open and tinker with config files directly, diagnosis and fixing finish in one flow.

Deeper — Tracing All the Way to Logs

/doctor → /debug

For a tricky problem whose cause even /doctor cannot pin down, move on to /debug (debug — a feature that shows the logs, the records of operation, in detail) to trace deeply. The order is to see the surface with diagnosis, and if it still does not resolve, look inside with the logs.

Real-World Example

After updating Claude Code, IDE integration suddenly stopped working. I was stuck not knowing what the problem was, so I ran this first.

/doctor

An integration-related item showed as a warning in the diagnosis result, and pressing f on the screen fixed it right away. What could have been an hour of wandering through settings was done with one diagnosis and one key.

Using It Further

• If something is off, diagnose first: When behavior is suspicious, run /doctor first instead of touching settings by guesswork.
• Auto-fix with f: When a problem is caught, fix it right away with the f key on the result screen.
• Check right after an update: Integrations often break after a version bump, so running it once after updating is reassuring.
• Link to debug if unresolved: For problems diagnosis cannot catch, trace all the way to logs with /debug.

Tip: Remember /doctor as the first command to come to mind when "an error of unknown cause occurred." Before wandering by pasting the error message into a search box, one diagnosis often solves half of it.

Summary

The core fits in one sentence. When something is off, do not wander; run /doctor first. It diagnoses installation and config on its own and fixes problems right there with the f key. For tricky problems that still do not resolve, trace all the way to logs with /debug.

Based on: Claude Code v2.1.154 (2026.05)