[BUG] extended thinking doen't work (think, think hard, think harder)
Status Fixed / completed
Maintainer reply None cached
Activity 15 comments · opened Sep 30, 2025 · closed Dec 9, 2025
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I've used Claude Code in wsl2. An hour ago, think, think hard worked very well. But after update to 4.5 sonnet, It doesn't work. I've typed think , think hard, think harder many times but CC doesn't think at all. How do I activate thinking mode?
What Should Happen?
It should work extended thinking.
Error Messages/Logs
Steps to Reproduce
input think but it doesn't think.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude Code version 0.5.1
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
15 Comments
This is absolutely cooked. What are they doingggg
I've got the same issue starting this morning after the new update
Same, in my understanding using tab to trigger thinking mode should act like this:
Thinking on: Uses thinking for all requests.
Thinking off: Thinking is off by default but when using a keyword like "think", "think hard", etc. Thinking should be enabled for the current request and put back to off after the answer.
Right now what I'm seeing is:
Thinking on: Always thinks, as expected
Thinking off: Never thinks even when using a keyword, does not work as expected
This change is horrible, they should reverter it
Interesting.
<img width="1499" height="529" alt="Image" src="https://github.com/user-attachments/assets/880f65d9-0b8f-4b8e-9887-efb6df6fb36e" />
Before of the update as soon as I wrote think..think harder, etc, the thinking mode were active, but I notice that now with Tab, idk if that is really new, or it was since the version 2
<img width="2836" height="214" alt="Image" src="https://github.com/user-attachments/assets/7fc7fd3f-c413-40db-9837-eecbb644c247" />
<img width="1193" height="87" alt="Image" src="https://github.com/user-attachments/assets/98e99ca0-6aca-45fb-a19f-b588f1712e55" />
it supports only Thinking(ultrathink) and not thinking
u can toggle by tab or write
ultrathinkin prompt<img width="1726" height="188" alt="Image" src="https://github.com/user-attachments/assets/289cf8dc-6f8e-4862-aff0-0b90c625e224" />
+1 Super annoying and terrible communication from Anthropic
If you turn thinking on with ‘Tab’, is that the same as typing ‘ultrathink’? Or is thinking mode a basic level of thinking and ‘ultrathink’ for more?
Totally unclear.
I use Claude Code with Visual Studio Code through native extension. In native, there is still no thinking mode shown.
There is only two mods right now. Thinking ON and thinking off, by default thinking is off, when u type ultrathink a thinking mode will be turned ON.
Either toggle it by using tab or writing ultrathink in prompt.
in claude code version 1 ultrathink was able to use too, many people just didnt use it because it uses maximum token, and tbh think harder was enought, but in claude code v2, they removed think, think hard and think harder mode, leaving only ultrathink and default no think
Horrible change. Only two levels of thinking (ultrathink and off) and no visual feedback which mode you are currently using. Token usage will skyrocket with all users now using ultrathink without knowing.
This horrible change for sure, not just because there are only 2 thinking modes and I have no click here in there at the beginning of each session but because we lost the ability to inject the keywords inside of our specs implicitly controlling the thinking budget.
Horrible change
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
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.