itâs actually a weird behavior on 1 of my computer itâs open the last opened project in the last mode but on the other one itâs always open the agent view
Cursor often gets to a point where I have to force quit it because it consumes too much memory. And when I do and I try to reopen it, it opens it back to the agents window which is completely useless but thatâs beside the point (I mean, I have claude code and codex Iâm not going to pay cursor their crazy amount of money that they would charge for API based usage for what I can get for a lot less directly from CC or OAâŠ).
So then I click Editor window again, but it completely forgets the state that the app was in. All of my open tabs, everything is completely lost. So dumb.
Same overe hereI donât want to use this stupid âAgent only / glass modeâ either; I just want the Editor. The Agent is being pushed so aggressively everywhere and itâs incredibly annoying - I absolutely do NOT want this âCursor Glassâ layout. Itâs terrible. I pay a lot of money for Cursor every month.
If I wanted something like that, Iâd use Codex or Claude Code. Iâm not choosing Cursor for this experience.
Since a recent update the cursor . command inside a folder from my terminal no longer opens the folder in editor mode, it just defaults to the agents window every time. I also tried cursor editor . with the same problem.
Cursor 3.3.27
Steps to Reproduce
Run cursor . command inside a folder on Mac
Expected Behavior
It opens the editor mode with the current folder loaded
Weâve received the feedback. Following up on that, version 3.3.30 adds a new âOpen Agents Window on startupâ toggle in Cursor Settings > Agents. Turn it off to launch into the Editor by default.
To get the update: Cmd/Ctrl+Shift+P > Attempt Update, then restart Cursor.
If you donât see the toggle after updating, the workarounds from my earlier reply still work: Shift+Cmd+N (Mac) / Shift+Ctrl+N (Windows/Linux) to open the Editor, or launch from terminal with cursor . --classic. The update is rolling out gradually, so it may take a bit to reach everyone.
My job is still to write and read code and I speak to robots occasionally whenever I need to .
Who guessed that by typing âcursor .â in my repoâs terminal I would have liked to open an agents window, press âeditor windowâ and select manually the repo Iâve just typed the command from?
Thanks for the workaround, waiting for 3.3.30 to be available for me and using âclassic until then
this is broken I turn off the toggle and i still am stuck with the agents when i open cursor
edit:
not broken, you have to switch the toggle off, move to the editor, close the agents and then close the editor, on next open editor opens by default.
A few notes on the issues raised since the toggle announcement.
cursor . from terminal : The startup toggle controls what opens when you launch Cursor from the dock or app icon. cursor . from terminal currently uses a separate path and opens the Agents Window regardless of the toggle. Weâre aware of this gap. For now, use cursor . --classic to open the Editor with your folder loaded.
Toggle not taking effect immediately: The toggle applies on the next fresh launch. Turn it off, fully quit Cursor (Cmd+Q on Mac, Alt+F4 on Windows), then reopen. You shouldnât need to manually switch windows first, but if the toggle doesnât stick after a restart, try the sequence @sxcq1222ssc described (turn off toggle, switch to Editor, close all Cursor windows, reopen).
Windows availability: The update is rolling out gradually and should reach everyone within the next few days. Until then, cursor . --classic or Shift+Ctrl+N after launch will get you to the Editor.
Same issue here:
Clicking the âOpen Editor Windowâ button on an agent now focuses an already-open editor window â often one belonging to a different, unrelated workspace or a stale worktree from a previous agent â instead of opening a new editor window for the current agentâs workspace. This makes it impossible to work with multiple agents in parallel, each in its own editor window, which used to work fine.
Expected behavior
Each agentâs âOpen Editor Windowâ opens a dedicated editor window for that agentâs workspace/worktree.
Multiple agents â multiple editor windows side by side, one per agent.
Actual behavior
The action reuses whichever existing window VS Codeâs window manager picks first, often unrelated to the agent I clicked from.
The only documented workaround is to close other editor windows, which defeats the multi-agent workflow entirely.
Impact
Multi-agent / multitask mode is effectively unusable for parallel work.
Workflow regression vs. previous versions where each agent reliably opened its own editor window.
Requests
Restore previous behavior: each agent opens its own editor window.
Or add a setting (e.g. cursor.agent.openEditorIn: "newWindow" | "reuse") so users can opt in.
At minimum, âOpen Editor Windowâ should never focus a workspace unrelated to the agent.