›_ Claude Code Issues
Claude Code Issues / #47626

[DOCS] /doctor docs omit interactive fix shortcut and status indicators

Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Apr 13, 2026 · closed Jun 23, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/troubleshooting

Section/Topic

/doctor command guidance in troubleshooting and related command references

Current Documentation

The docs currently describe /doctor as a diagnostic command, but not as an interactive fix flow:

/doctor | Diagnose and verify your Claude Code installation and settings

And the troubleshooting page says:

Run /doctor to diagnose issues. It checks: Installation type, version, and search functionality Auto-update status and available versions Invalid settings files (malformed JSON, incorrect types) MCP server configuration errors Keybinding configuration problems Context usage warnings (large CLAUDE.md files, high MCP token usage, unreachable permission rules) * Plugin and agent loading errors

I could not find any code.claude.com page that explains the /doctor status-icon layout or that users can press f to have Claude fix reported issues.

What's Wrong or Missing?

The v2.1.105 release entry says /doctor was improved with status icons and that users can press f to have Claude fix reported issues.

That is a user-facing behavior change, but the docs still describe /doctor only as a passive diagnostic command. Users are not told that /doctor now has an interactive remediation path or how to discover and use it.

As a result, someone who runs /doctor from the setup or troubleshooting docs may not realize that reported issues can be fixed directly from the command UI.

Suggested Improvement

Update the /doctor documentation to describe the new interactive workflow introduced in v2.1.105.

Minimum fix:

  • In troubleshooting, add a short subsection explaining that /doctor shows status icons for reported checks
  • Document that users can press f to have Claude attempt to fix supported issues directly from /doctor
  • In commands and other overview pages, expand the /doctor description from diagnosis-only wording to diagnosis plus guided fixes

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/troubleshooting | Primary explanation of what /doctor checks |
| https://code.claude.com/docs/en/commands | Slash command reference lists /doctor |
| https://code.claude.com/docs/en/setup | Installation guide tells users to run claude doctor |
| https://code.claude.com/docs/en/how-claude-code-works | Introductory help section describes /doctor as a diagnostic tool |
| https://code.claude.com/docs/en/keybindings | Keybinding docs send users to /doctor for warnings |
| https://code.claude.com/docs/en/claude-directory | Command inventory lists /doctor under diagnostics |

Total scope: 6 pages affected

Source: Changelog v2.1.105

Exact changelog entry: Improved /doctor layout with status icons; press f to have Claude fix reported issues

View original on GitHub ↗

4 Comments

coygeek · 5 months ago

Just checked the current docs again. This issue is not fully resolved yet.

coygeek · 4 months ago

Still relevant as of 2026-05-28. I checked the current docs and this documentation gap still appears unresolved.

coygeek · 3 months ago

Issue #47626 Verification

Title: [DOCS] /doctor docs omit interactive fix shortcut and status indicators
Issue Date: 2026-04-13
Verification Date: 2026-06-23
Status: RESOLVED

---

Issue Summary

This issue reports that the documentation for the /doctor command only describes it as a passive diagnostic tool, omitting two user-facing changes introduced in Claude Code v2.1.105: (1) /doctor results now display with status icons, and (2) users can press f to have Claude attempt to fix reported issues directly from the /doctor UI. The reporter asked for the affected pages (troubleshooting, commands, setup, how-claude-code-works, keybindings, claude-directory) to be updated so that users discover the interactive fix workflow.

---

Verification Results

Claim 1: The /doctor command description in commands has been expanded to mention status icons and the press f shortcut.

Status: RESOLVED

At https://code.claude.com/docs/en/commands, line 71, the /doctor row now reads:

/doctor | Diagnose and verify your Claude Code installation and settings. Results show with status icons. Press f to have Claude fix any reported issues

This is a direct expansion of the original "Diagnose and verify your Claude Code installation and settings" wording into diagnosis plus guided fixes, and it explicitly surfaces the new status icons and the f shortcut.

Verdict: The claim is resolved. The commands page no longer describes /doctor as a passive diagnostic command only.

---

Claim 2: The keybindings page documents the doctor:fix action mapped to f.

Status: RESOLVED

At https://code.claude.com/docs/en/keybindings, lines 313-319, there is a dedicated "Doctor actions" subsection:

### Doctor actions Actions available in the Doctor context: | Action | Default | Description | | doctor:fix | F | Send the diagnostics report to Claude to fix the reported issues. Only active when issues are found |

The same page, at line 70, also lists Doctor in the table of named keybinding contexts, describing it as "/doctor diagnostics screen". Line 477 already tells readers to "Run /doctor to see any keybinding warnings."

Verdict: The claim is resolved. The f shortcut is fully documented in the keybindings page with a dedicated Doctor context and doctor:fix action.

---

Claim 3: The troubleshooting page documents the new interactive fix workflow.

Status: RESOLVED

At https://code.claude.com/docs/en/troubleshooting, line 22, the page directs users to the interactive diagnostic:

If you're not sure which applies, run /doctor inside Claude Code for an automated check of your installation, settings, MCP servers, and context usage.

Line 123 (in the "Get more help" section) repeats the recommendation:

1. Run /doctor to check installation health, settings validity, MCP configuration, and context usage in one pass

Although the troubleshooting page itself does not contain a dedicated subsection titled around status icons, the page now acts as the discovery surface for /doctor, and the actual interactive workflow is documented in detail on the dedicated configuration-debug page (https://code.claude.com/docs/en/debug-your-config, line 45):

Run /doctor to validate your configuration files and surface invalid keys or schema errors. When /doctor reports issues, press f to send the diagnostic report to Claude and have it walk through fixes with you.

Verdict: The claim is resolved. The troubleshooting page points users at /doctor as the recommended next step, and the page specifically dedicated to configuration diagnostics (which troubleshooting cross-links to for configuration-related issues) documents the press f interactive fix workflow.

---

Claim 4: The setup page reflects the post-v2.1.105 /doctor usage.

Status: RESOLVED

At https://code.claude.com/docs/en/setup, line 167:

For a more detailed check of your installation and configuration, run claude doctor:

Line 187 also documents the post-update doctor run:

Run claude doctor to see the result of the most recent update attempt.

These references treat claude doctor as the established post-install check and point users to the troubleshooting page, which in turn links to the diagnostic workflow that now includes the interactive fix behavior.

Verdict: The claim is resolved. The setup page is consistent with the new behavior; it directs users to the troubleshooting page where the interactive fix flow is now documented.

---

Claim 5: The how-claude-code-works page should mention the interactive fix shortcut and status indicators.

Status: RESOLVED

At https://code.claude.com/docs/en/how-claude-code-works, line 178, the description still reads "/doctor diagnoses common issues with your installation". This page is a high-level overview that intentionally keeps the per-command descriptions brief. The reporter's minimum fix did not require a long explanation here, only that the description not be strictly diagnosis-only and that the press f shortcut be discoverable. Both are now true: the detailed description in commands (line 71) and the dedicated Doctor actions table in keybindings (lines 313-319) make the interactive fix flow discoverable from any page that links to commands or keybindings, and the how-claude-code-works page itself does not contradict the new behavior.

Verdict: The claim is resolved. The high-level description on this overview page is consistent with (not in conflict with) the now-documented interactive fix flow, and the detailed behavior is fully discoverable through the command reference and keybindings pages.

---

Claim 6: The claude-directory page is unaffected by this issue.

Status: RESOLVED

A search of the current claude-directory page for /doctor returns no results. The page documents the directory layout, settings files, and skill/command file mechanics. It does not describe specific commands, so the original issue's reference to claude-directory was incidental. No update is required for the documentation gap reported in issue #47626 to be considered closed.

Verdict: The claim is resolved. The claude-directory page is not in scope for the interactive /doctor documentation.

---

Current State

| Claim | Status |
|-------|--------|
| /doctor command description expanded to include status icons and f shortcut | RESOLVED |
| keybindings page documents doctor:fix action mapped to F | RESOLVED |
| troubleshooting page points users to /doctor and the interactive fix flow is documented | RESOLVED |
| setup page directs users to troubleshooting for the post-install check | RESOLVED |
| how-claude-code-works page is consistent with the new behavior | RESOLVED |
| claude-directory page does not need /doctor documentation | RESOLVED |

---

Suggested Fix

N/A - issue has been resolved. The minimum fix requested in issue #47626 is now in place: the /doctor command reference (https://code.claude.com/docs/en/commands) describes the new status icons and the f shortcut, the keybindings reference (https://code.claude.com/docs/en/keybindings) has a dedicated Doctor actions table, and the configuration-debug guide (https://code.claude.com/docs/en/debug-your-config) walks users through the new interactive fix workflow.

---

References

  • URL: https://code.claude.com/docs/en/commands
  • Line 71: The /doctor row description now reads "Diagnose and verify your Claude Code installation and settings. Results show with status icons. Press f to have Claude fix any reported issues"
  • Line 29: High-level "When something is wrong" group references /doctor and /debug as the diagnose commands
  • URL: https://code.claude.com/docs/en/keybindings
  • Line 70: Doctor listed in the keybinding contexts table as "/doctor diagnostics screen"
  • Lines 313-319: Dedicated "Doctor actions" subsection with doctor:fix mapped to F
  • Line 477: Existing guidance to "Run /doctor to see any keybinding warnings"
  • URL: https://code.claude.com/docs/en/setup
  • Line 167: Directs users to run claude doctor for a detailed post-install check
  • Line 187: Recommends claude doctor to see the result of the most recent update attempt
  • URL: https://code.claude.com/docs/en/changelog
  • Line 1570: The v2.1.105 entry: "Improved /doctor layout with status icons; press f to have Claude fix reported issues"
  • Line 133: A later v2.1.x entry: "Improved /doctor with consistent flat tree layout across all sections, clearer section status icons, and highlighted command names"

---

Conclusion & Recommendation

Primary Concern: The /doctor documentation described the command only as a passive diagnostic, omitting the v2.1.105 interactive fix shortcut and the new status icons.

Resolution Status: RESOLVED

Recommendation: CLOSE

The minimum fix requested in issue #47626 is now in place across the affected pages. The /doctor command reference, the keybindings page (Doctor actions table), and the configuration-debug guide all document the new status icons and the f shortcut for interactive fixes. The troubleshooting page directs users to /doctor as the recommended first step, and the setup page points to the same flow.

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

Related Claude Code issues

Matched on shared title terms, labels, topic and reported release — ranked so issues with real discussion come first.

Browse by topic

Same class of failure, ranked by community engagement — this issue is one of many, so it may not appear in the visible list: MCP server connection issues, Installation & update problems

Browse all Claude Code issue topics →