claude-code - 💡(How to fix) Fix [DOCS] Code intelligence docs omit click-to-expand LSP diagnostic summaries [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54170Fetched 2026-04-29 06:34:25
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Error Message

  • Automatic diagnostics: after every file edit Claude makes, the language server analyzes the changes and reports errors and warnings back automatically. Claude sees type errors, missing imports, and syntax issues without needing to run a compiler or linter. If Claude introduces an error, it notices and fixes the issue in the same turn. This requires no configuration beyond installing the plugin. You can see diagnostics inline by pressing Ctrl+O when the "diagnostics found" indicator appears.
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/discover-plugins

Section/Topic

What Claude gains from code intelligence pluginsAutomatic diagnostics

Current Documentation

The docs currently say:

  • Automatic diagnostics: after every file edit Claude makes, the language server analyzes the changes and reports errors and warnings back automatically. Claude sees type errors, missing imports, and syntax issues without needing to run a compiler or linter. If Claude introduces an error, it notices and fixes the issue in the same turn. This requires no configuration beyond installing the plugin. You can see diagnostics inline by pressing Ctrl+O when the "diagnostics found" indicator appears.

The terminal shortcuts page also says:

| Ctrl+O | Toggle transcript viewer | Shows detailed tool usage and execution. Also expands MCP calls, which collapse to a single line like "Called slack 3 times" by default |

These pages mention automatic diagnostics and Ctrl+O, but they do not document the new click-to-expand behavior for LSP diagnostic summaries or the new expand hint in the UI.

What's Wrong or Missing?

Changelog v2.1.121 added a new interaction for inline LSP diagnostics:

LSP diagnostic summaries now expand on click/ctrl+o and show the expand hint

The current documentation tells users that diagnostics appear after edits and that Ctrl+O opens the transcript viewer, but it does not explain that diagnostic summaries themselves can now be expanded directly by clicking them, nor that Claude Code shows an expand hint to advertise that interaction.

That leaves the new behavior undiscoverable for users who rely on inline diagnostics while editing with code intelligence plugins enabled.

Suggested Improvement

Update the code intelligence documentation to describe how inline LSP diagnostic summaries behave in v2.1.121 and later.

For example, the Automatic diagnostics section could add a note like:

When the diagnostics found indicator appears, open the diagnostic summary with Ctrl+O or click the summary directly. Claude Code now shows an expand hint when more detail is available.

The terminal interaction docs should also mention that Ctrl+O can expand LSP diagnostic summaries in addition to opening the verbose transcript.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/discover-pluginsPrimary code intelligence page describing automatic diagnostics after edits
https://code.claude.com/docs/en/interactive-modeCtrl+O shortcut reference should mention LSP diagnostic summary expansion behavior
https://code.claude.com/docs/en/tools-referenceLSP tool behavior section describes automatic diagnostics but not how users expand the summaries

Total scope: 3 pages affected

Source: Changelog v2.1.121

Exact changelog entry:

LSP diagnostic summaries now expand on click/ctrl+o and show the expand hint

extent analysis

TL;DR

Update the code intelligence documentation to describe the new behavior of inline LSP diagnostic summaries in v2.1.121 and later.

Guidance

  • Review the Automatic diagnostics section in the code intelligence documentation and add a note explaining that diagnostic summaries can be expanded by clicking them or using Ctrl+O.
  • Update the terminal interaction documentation to mention that Ctrl+O can expand LSP diagnostic summaries in addition to opening the transcript viewer.
  • Verify that the changes are reflected on all affected pages, including the primary code intelligence page, interactive mode page, and tools reference page.
  • Consider adding a note about the expand hint that appears when more detail is available for LSP diagnostic summaries.

Example

The updated Automatic diagnostics section could include a note like:

When the diagnostics found indicator appears, open the diagnostic summary with Ctrl+O or click the summary directly. Claude Code now shows an expand hint when more detail is available.

Notes

The changes should be made to the following pages: https://code.claude.com/docs/en/discover-plugins, https://code.claude.com/docs/en/interactive-mode, and https://code.claude.com/docs/en/tools-reference.

Recommendation

Apply workaround: Update the documentation to reflect the new behavior of inline LSP diagnostic summaries, as this will improve the discoverability of the feature for users who rely on inline diagnostics.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING