When i have an agent create a plan and then it builds on the plan it will make a lot of code changes. Before it used to show me all those code changes in the chat, now it hides those code changes behind a “Worked for X ” accordion (which doesn’t even look like an accordion until you hover over it.
Steps to Reproduce
Make a plan and ask the agent to do it.
Expected Behavior
Just show me the changes, or give me the option to see the changes the agent is making. Don’t hide it from me.
Hi @zanawar Thank you for the forum post! I believe this is intended behavior, not a bug, but it’s something we’ve implemented as agents become more autonomous and work for longer on their own. This is meant to improve the UX rather than presenting you with a deluge of changes all at once, but it is still easily accessible when you expand it.
There’s been times when i’ll ask an agent to do something, and it just talks to me; doesn’t actually do anything. I could easily tell when this happened because I’d see no code changes. Now I’m always uncertain whether it actually made a change or is just wasting time.
Changes to plan always cause this behavior. I ask it to evaluate something in the plan. “Worked for 2m 33s” okay but did it make any changes? I have to open the accordion to see.
I really don’t see how this improves UX. My user experience is now I can’t easily tell if the agent has made changes or not. Sure i can go click the button, but now I get to click some smaller text, that also has lower contrast. This is not a deluge of changes which has been hidden from me, this is a singular, very relevant change, that has now been hidden from me.
I agree with the original poster that this is actually worse UX. I want to see the changes cursor is making to the codebase when I read through the chat window, having it obscured behind an accordion add more steps for me to see these changes. I understand that the Cursor team is continually trying to improve the UI/UX in ways they feel would be useful, but for something like this, it should be an option users can switch on/off
This should be a setting that we can choose. Default it to whatever you think is best for the product, but we should have a choice. Why this choice matters:
Engineers (literally) – or if you prefer “Classically Trained Engineers” since “engineer” is ridiculously overused – demand that nothing be hidden. We don’t believe in magic nor do we trust magic. We need to know what is going on because we are the ones accountable for anything that happens. So much happens with coding AI agents and having these visual cues works wonders for us actual human beings!
Obviously there are other ways to check if edits are made, i.e. git status. But that shouldn’t be the only way we can find out – having passive visual cues are extremely helpful. Zachary’s post highlights the advantages pretty clearly.
I can understand that business level stakeholders want this to all appear magical to us and that hiding things does serve that end. But us engineers can never and will never accept that.
I should add that when using Grok 4.5, this is not occurring. It’s showing file edits like Cursor always has been (i.e. a 4 or 5 line snippet). Likely because Grok isn’t fully integrated yet (a.l.a not yet able to use the AskQuestions UI thing).
