“After the thinking process completes, it is displayed like this. However, when I click on it, the thinking content is not shown.”
Hi there!
We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.
To help us investigate and fix this faster, could you edit your original post to include the details from the template below?
Bug Report Template - Click to expand
Where does the bug appear (feature/product)?
- Cursor IDE
- Cursor CLI
- Background Agent (GitHub, Slack, Web, Linear)
- BugBot
- Somewhere else…
Describe the Bug
A clear and concise description of what the bug is.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
- …
- …
- …
Expected Behavior
What is meant to happen here that isn’t working correctly?
Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
Operating System
- Windows 10/11
- MacOS
- Linux
Version Information
- For Cursor IDE: Menu → About Cursor → Copy
- For Cursor CLI: Run
agent aboutin your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......
CLI:
CLI Version 2026.01.17-d239e66
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
- Yes - Cursor is unusable
- Sometimes - I can sometimes use Cursor
- No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hi @Abdelrahman_Mohamed, I don’t know why @system flagged it as a bug report, this line is usually just a placeholder that wait for though element to come back to the agent window, after that there is a thought line that appears and that can be clicked on properly, tell me if you get what I mean by that
Hey @Abdelrahman_Mohamed!
This was a super interesting one. Thanks for reporting it! 
I dug into it, and it looks like the issue happens when the model’s reasoning is immediately followed by a tool call (with no assistant text in between). In that case, the thought never gets a recorded duration, and the UI shows it as a non-clickable “Thought briefly”, so the reasoning is actually there; it just can’t be expanded!
To confirm we’re looking at the same thing: was there a tool call right after your “Thought briefly”? For example, in the screenshot below the thought was immediately followed by a WebSearch call:
I’ve filed a bug for this.