I wasn’t able to reproduce this on my end - closing the chat panel returns focus to the editor as expected. Could you share a short screen recording showing the issue? Also, does this happen consistently or only in certain scenarios (e.g., specific file types open, multiple editor groups, etc.)?
Since you’re on nightly (2.7.0-pre.105), it might also be worth checking if the issue persists after restarting Cursor.
This is an accessibility issue for blind users - using cursor with Screenreader (NVDA).
This started from one of the recent versions (I started experiencing this about a week ago).
This makes cursor much harder to use for blind people because we lost an ability to jump between chat and main editor in a single keystroke. In the end I found a workaround, but it involves tens of keystrokes - I have to open file explorer and find the right file there. Very tedious.
Steps to Reproduce
Run Cursor on Windows, use NVDA screen reader. Turn on accessibility mode in Cursor.
Open some file. Press control+L to open chat pane.
Try to go back to the editor using keyboard commands only. No mouse.
Expected Behavior
Pressing control+L again should take you back to editor pane. In fact, it closes the chat pane visually, but it doesn’t focus the main editor.
Pressing control+shift+E twice should also take you back to the main editor - that’s VSCode command. In fact, the focus gets stuck in the file explorer pane.
For AI issues: add Request ID with privacy disabled
N/A
Additional Information
I’m hoping this issue will get some attention. There are not many AI coding tools that are accessible to blind people. Cursor is one of them - in general accessibility is pretty good. But this recent regression slows me down significantly.