Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
In the most recent version, 3.10.20, agent tool call information is buried even further in the agent window with an ‘Explored (x) tools’ message (where ‘x’ is the number of tools explored/used), making it even more difficult for users to see the agent and MCP interactions that are happening.
This is in defiance of having ‘Conversation Density’ set to ‘Detailed’, which should fully expand these interactions in the agent window.
Steps to Reproduce
- Update to 3.10.20
- Set Conversation Density (“Choose how much detail agent tool calls show in the conversation”) to Detailed.
- Try to make a tool / MCP call.
- Observe that the setting isn’t honored, and all information is now obscured underneath an ‘Explored…’ toggle that must be expanded several times before agent / MCP interactions can be seen.
Expected Behavior
All tool calls and MCP interactions should be fully expanded when the ‘Detailed’ setting is set. However,
Screenshots / Screen Recordings
![]()
Operating System
Linux
Version Information
Version: 3.10.20
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 6.8.0-124-generic
For AI issues: which model did you use?
N/A
Additional Information
Meta comment: I’ve filed a variant of this bug on at least one other occasion. Beyond this bug, it appears that Cursor has made a decision to actively abstract and hide useful info from users – and this seems to be getting worse in recent versions.
Especially for users in Editor mode (who are presumably experienced developers), the default should be to show everything – all command line output, all agent output by default, rather than dumbing down the interface to appeal to less technically inclined users who’d likely use the Agent window anyway.
Does this stop you from using Cursor
No - Cursor works, but with this issue