claude-code - 💡(How to fix) Fix VS Code extension: thinking blocks render without expand chevron [2 comments, 3 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#55120Fetched 2026-05-01 05:45:44
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Timeline (top)
labeled ×5commented ×2

In the VS Code extension chat panel, extended thinking blocks render with their status label (e.g., Thinking..., Imagining...) but without the disclosure chevron / twisty that previously allowed expanding them to view the reasoning content. Both click-to-expand and the documented Ctrl+O shortcut fail because there is no clickable disclosure target in the rendered DOM.

This was working previously in the same install. The regression appeared without any deliberate configuration change on my side.

Error Message

Error Messages/Logs

Root Cause

In the VS Code extension chat panel, extended thinking blocks render with their status label (e.g., Thinking..., Imagining...) but without the disclosure chevron / twisty that previously allowed expanding them to view the reasoning content. Both click-to-expand and the documented Ctrl+O shortcut fail because there is no clickable disclosure target in the rendered DOM.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Summary

In the VS Code extension chat panel, extended thinking blocks render with their status label (e.g., Thinking..., Imagining...) but without the disclosure chevron / twisty that previously allowed expanding them to view the reasoning content. Both click-to-expand and the documented Ctrl+O shortcut fail because there is no clickable disclosure target in the rendered DOM.

This was working previously in the same install. The regression appeared without any deliberate configuration change on my side.

Expected behavior

Per the VS Code extension docs:

Claude's reasoning appears in the conversation as collapsed blocks: click a block to read it, or press Ctrl+O to expand or collapse every thinking block in the session.

A disclosure chevron should render to the left of the status label, and clicking the block should expand it to reveal the reasoning content.

Actual behavior

The Thinking... and Imagining... status labels render as plain text only. No chevron, no disclosure triangle, no clickable affordance. Clicking the label does nothing. The reasoning content is not reachable from the UI. Screenshot attached.

Steps to reproduce

  1. Open a Claude Code session in the VS Code extension chat panel
  2. Ask a prompt that exercises extended thinking (a non-trivial design or reasoning task)
  3. Observe: Thinking... / Imagining... indicators render but have no expand control

Environment

  • Claude Code extension: 2.1.123 (win32-x64)
  • VS Code: 1.115.0 (user setup), commit 41dd792b5e
  • OS: Windows 11 Pro (10.0.26200)
  • Model: Claude Opus 4.7 (1M context)

What I already tried

  • Restarting VS Code — no change (regression first observed after a routine restart)
  • Command Palette → Developer: Reload Window — no change
  • Searched claudeCode.* and .claude/settings.json for a thinking-display toggle — none exists in the extension

Additional context

The regression appears to be extension-side rendering — the model continues to produce thinking content (the status indicators advance through phases like Thinking...Imagining...), but the UI has stopped rendering the disclosure control around it. Likely candidate causes: a recent extension release that touched chat panel rendering, or an interaction with Opus 4.7's interleaved thinking format. Older obsolete versions on disk include 2.1.109, 2.1.114, 2.1.116, 2.1.117, 2.1.119, 2.1.120 — bisecting against those should isolate the regression.

What Should Happen?

A disclosure chevron / twisty should render to the right of the Thinking... status label, making the block expandable. Clicking the block (or pressing Ctrl+O) should expand it to show the reasoning content, per the VS Code extension docs which say: "click a block to read it, or press Ctrl+O to expand or collapse every thinking block in the session."

Error Messages/Logs

Steps to Reproduce

  1. Open a Claude Code session in the VS Code extension chat panel
  2. Ask a prompt that exercises extended thinking (a non-trivial design or reasoning task)
  3. Observe: Thinking... / Imagining... indicators render but have no expand control

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.123 (win32-x64)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

<img width="578" height="71" alt="Image" src="https://github.com/user-attachments/assets/b7f35be2-e0d0-4e41-b0b4-8a5f94052abb" />

extent analysis

TL;DR

The issue can likely be resolved by downgrading the Claude Code extension to a previous version where the disclosure chevron was rendering correctly, such as version 2.1.117 or earlier, to restore the expandable thinking blocks in the VS Code chat panel.

Guidance

  • Verify the regression: Confirm that the issue is indeed a regression by checking if the disclosure chevron was present in a previous version of the Claude Code extension.
  • Bisect the versions: Try downgrading the extension to one of the older versions mentioned (e.g., 2.1.109, 2.1.114, 2.1.116, 2.1.117, 2.1.119, 2.1.120) to identify the exact version where the regression occurred.
  • Check for updates: Look for any updates to the VS Code extension or the Claude Code documentation that might address this issue or provide a workaround.
  • Report the issue: If downgrading resolves the issue, report the findings to the developers, including the version where the regression occurred, to help them identify and fix the problem.

Example

No code snippet is provided as the issue seems to be related to the rendering of the UI components in the VS Code extension, which is not directly related to user-written code.

Notes

The solution involves downgrading the extension, which might temporarily resolve the issue but does not address the root cause. The developers should be notified so they can fix the regression in future updates.

Recommendation

Apply the workaround by downgrading the Claude Code extension to a version known to work, such as 2.1.117 or earlier, until an updated version that fixes the regression is released. This is recommended because it provides a temporary solution to restore functionality while waiting for a permanent fix.

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…

FAQ

Expected behavior

Per the VS Code extension docs:

Claude's reasoning appears in the conversation as collapsed blocks: click a block to read it, or press Ctrl+O to expand or collapse every thinking block in the session.

A disclosure chevron should render to the left of the status label, and clicking the block should expand it to reveal the reasoning content.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix VS Code extension: thinking blocks render without expand chevron [2 comments, 3 participants]