[FEATURE] VS Code plugin - 'Thinking' text rate throttle

Resolved 💬 2 comments Opened Mar 11, 2026 by nukamoi Closed Apr 9, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When I'm working with Claude Code plugin in VS Code, I prefer to read all of Claude's reasoning text (requires expanding the "thinking" content) because sometimes the path taken or the reasoning is not correct (or at least not what I had in mind). I find that I cannot read the thinking text as quickly as Claude produces it.

Proposed Solution

I would like to be able to throttle (slow down) the rate at which Claude produces the "thinking" text so that I can keep up with the reasoning. This should be an option in the plugin settings.

Reading the thinking text after it is all produced (e.g. using /export) is not an acceptable solution because the reasoning consumes tokens/context which is wasted when Claude takes the wrong path.

Alternative Solutions

Claude not taking the wrong path in its reasoning?

_That's a sarcastic comment because of course that's completely unreasonable since Claude's reasoning depends on the quality of my prompts and the previous context_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

  • I'm working on a web app for my team (vanilla JS / HTML / CSS)
  • I ask Claude to make a change (e.g. to a JS function) which has knock-on impacts to other sections of the code base
  • Claude reasons that the knock-on impacts should be handled in a certain way
  • I miss this reasoning because the "thinking" text flies by too quickly
  • I have to re-prompt Claude to undo the changes it made
  • My token / context consumption increases more than necessary

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗