With Editor Window I can see what files changed in that thread.
With Agents Window I can’t.
I propose you bring that feature/capability from Editor window because:
I have a personal context for each chat. E.g. one is about UI, another one is about backend. each touch different files
If I want to review changes and all the agent thread touched files are mixed up, is really hard to make sense of the story and decide.
Currently I don’t trust what the agent produces, specially on mission critical systems. I want to review and make sure it’s correct. Even when it’s correct, seeing what the thread decides helps me understand how to steer it.
Right now I have to go to the Editor Window to do those verification but it’s tedious.
Thank you for the note, @bernatfortet! We’ve received a few similar requests and have added your thread to the ticket where we’re collecting that feedback.
Hi @Colin looks like now the “Review” experience in the Editor Window has regressed and it’s either missing files from touched by the thread, or showing them as already accepted/reviewed.
Now I need to go back to reviewing with a Git diff viewer which feels like a big regression.
Before with Editor Window at least I could see the changes related to the thread and have a conversation to change any issues. Now I have to manually re-craft the context by at mentioning files and even then I loose sight of the different relation/connections of files touched.
It feels like a large regressions that nudges people to blindly accept code. And I guarantee that 100% of the times there are issues with the code and/or architecture.
Regardless, thanks for all your work. Without cursor I would not have my own company.
I have exactly the same problem and it’s very inconvenient!
I want to see exactly what the Cursor agent changed in the code in the Cursor project window when the task was run in the Agents Window.