cursor 3 why does it default to the browser. i work on files in my code editor. does someone out there work entirely in a browser on their files?
When I open a new agent, there is never a world where i want everything i was doing closed. Let me choose what stays open. Such as just the file hierarchy. It’s great if per agent all the files close and we start fresh. But the file heirarchy needs to be locked into what i was doing. I edit files. I don’t know what your agents edit. But mine edit files. If i’m going to edit files. I would like to be able to see my files when i’m interoping with my agents.
I need to move files. I can no longer move files via cursor 3
i can no longer drag and drop files via cursor 3
i’ll be looking at changes and it’ll jump me to the new thing being edited if an agent is working. I would like to read the changes i’m working on.
it’ll consume keyboard presses as multiple files are being changed. System wide. I’m on arch linux
no button to do voice to text if I’ve typed prior. i have to one shot all of my voice work. and then nail all of my skills i need. in order.
let me do voice to text at any cursor position in my text window, and start and stop it freely just as before.
every time i open a new agent it closes everything. keep the file hierarchy the same. closing all the files is good. moving my file hierarchy is not. I work on files via cursor
what do you guys work on?
Hey, thanks for the detailed feedback. I’ll go point by point:
Default to browser / agents window: Cursor 3 Glass really works differently. Each agent has its own workspace context. If you prefer a file centric workflow, you can switch to the Editor layout: Ctrl+Shift+P then Open Editor Window. Editor mode keeps the usual behavior with the file tree.
File hierarchy resets when switching agents: This is by design in Glass. Each agent session has its own set of files and context. Editor mode keeps the file tree between sessions. I’ll pass along that this adds real friction for file heavy workflows.
Drag and drop not working: Known issue, the team is aware. Workaround: use @ in chat to add files as context, or move files via the terminal or the File Explorer context menu.
Agent changes stealing focus during review: Also on the radar. There was a recent fix for focus stealing during terminal commands, but the review changes issue might be a regression. Can you share the Request ID from a session where this happens? It’ll help the investigation.
Keyboard presses being consumed system wide on Arch Linux: That’s a serious symptom. Can you confirm if it happens in Glass layout or in Editor too? Are you on X11 or Wayland? Also, what exact Cursor version are you on?
Voice to text: I get that you used to be able to start and stop it freely anywhere. I’ll share this with the team, specifically that voice input can’t be used after you’ve already started typing.
Overall, if your workflow is very file focused, Editor mode will feel closer to how it worked before. Glass is more agent first. You can switch between them.
Let me know if you want help with a specific issue.
Can you tell me specifically. when you open cursor. what do you edit? I need to know that you understand you sell a file editor. There is no telling customers to do it the old way. If you are offering the better way to edit files. you have to own it. Like what’s the point of a revert button, if you aren’t reading the files ever? what would be reverted? the user would never know
to recreate system wide keyboard consumption, i was running 5 concurrent agents all doing a combination of over 100 file edits. it’s not something i can easily recreate, nor provide id’s for. Why so much so many? refactoring my skills into otel-itil hierarchies. breaking apart my 40 skills into hierarchical 150+ skills with interlinkages, since the agents are so good at opening and reading files now. And I can explain more what I’m doing in plain english. I’m an open source kind of guy if there’s interest.
The commit and push button is a miracle sent from God himself. If they can hammer out their intentions with the product, embrace the file hierarchy. They’ll be in a good place. I know it looks like I’m bashing the product but there’s more i like than what i dislike. The pain points are very painful, but the good vastly exceeds the pain. I will continue to use cursor 3 and add feedback as the thing develops here in the next few weeks. reserving final judgement until then
conversely there’s another way to think about the problem entirely. double down on ‘we’re making the perfect agent surface’ and the expectation is that on one monitor you have the agentic surface and the other monitor you have the files, git tree, and file hierarchy. and making them interplay nicely, so i can drag and drop folders from the vs code utility over to the new cursor 3 interface. however that one sounds much harder to me, and like a more long term project than just getting the next best file editor experience nailed. I know you guys got this whatever the decision gets made on