Problem
My primary workflow is in the Agents Window (Glass) — I run multiple agents in parallel and it’s great for orchestrating work. But when an agent surfaces something interesting and I need to dive deep into the code (trace a call chain, read surrounding context, set breakpoints, compare files side-by-side), I need the classic editor.
Today, switching means:
Cmd+Shift+P → “New Window” (or cursor --classic)
Manually find and re-open the chat I was looking at
Scroll to wherever I was in the conversation
Lose my mental context during the transition
This friction discourages me from going deep — I end up staying in Glass and asking the agent to explain things instead of reading the code myself, which is often slower and less effective.
Proposed Solution
Cmd+O (or a dedicated keybinding) in the Agents Window that:
Opens the classic editor window in the same workspace
Automatically opens the chat panel on the side
Scrolls the chat to the exact same position in the conversation timeline I was viewing in Glass
Ideally focuses the file(s) the agent last touched or referenced
The result: a zero-friction bridge from Glass → Editor, preserving full conversational context.
Why This Matters
Glass and the Editor are designed for different cognitive modes:
Mode Interface When
Orchestrate
Agents Window
Dispatching tasks, reviewing summaries, running parallel agents
Investigate
Classic Editor
Reading code, tracing logic, debugging, manual edits
Right now these two modes are disconnected. This feature would make them one continuous workflow — start broad in Glass, go deep in the Editor, come back to Glass. Best of both worlds.
Thanks for the idea! A keybinding for this makes a lot of sense. Switching between the Agents Window and the editor hasn’t been top a priority for us so far, but we totally get why people would want it (we do it ourselves!).
Just to make sure you’ve seen it (because it’s rather hidden), have you tried right-clicking on a workspace and selecting “Open in Editor Window”?
Thanks for the answer.
I didn’t know this option, but it does not really help. Because I am using worktree a lot. I would like to open the editor in the worktree of the chat. (So right click on the chat, not the workpace, to not have to select one in the looong list like here”
I am also running into the problem. One of the differentiatiors of Cursor vs. other AI Coding tools is that it has a good editor. But in the current release you can’t get to that editor any more in an efficient way.
Agent edits a file. I am not sure this is a good edit and want to look at the file. Display in the right pane is not wide enough on my laptop screen to see what’s going on. Now I want to open a full-screen capable editor and this takes forever. Find the right worktree, open a classic editor window for that worktree, navigate to the right file which may be buried deep in the tree.
My suggestion would be that right-clicking on any file (in chat, file browser or tab header) should have an “Open in Editor” option.
Not trying to brush aside your request (think it’s great to have feedback on this!), but would like to make sure you’ve seen the Word wrap setting in the Agents Window.
Thanks for the reply Colin, I appreciate it. Word wrap is on, but for nested blocks that only helps so much. See attached screenshot. I can make this a little better by closing side bars, but it’s still not pretty.
Cursor’s strength is that it has a great editor, all you need to do is give users a way to open it.
Edit: And to be clear, this screenshot shows the layout with minimum column sizes for the other three columns. This is the maximum I can get for the editor.
