After starting a Vite React dev server, Cursor auto‑opens a browser tab. If I click that browser tab to focus it and then close it immediately (without focusing anything else), returning to Cursor leaves the editor keyboard input broken (Cmd+Z, Backspace, arrows). Keybindings resolve but are not dispatched. Reloading the window fixes it temporarily.
If I first refocus Cursor (click anywhere in the editor UI) and then close the browser tab, the issue does not reproduce.
Steps to Reproduce
Open Cursor and any Front‑End React project.
Start a Vite React dev server (e.g., npm run dev).
Cursor auto‑opens a browser tab (e.g., http://localhost:4200).
Click the browser tab to focus it, then close it immediately (do not focus anything else first).
Return to Cursor editor and try Cmd+Z, Backspace, Arrow keys.
Expected Behavior
Browser tab releases focus after being closed.
Editor keybindings work normally.
Hey, thanks for the report. This is a known issue: the browserViewFocused flag can get stuck on true after certain interactions with the browser tab or AI chat, and that blocks keyboard shortcut dispatch.
Your case, closing an auto-opened tab without refocusing the editor first, is a new specific trigger. That’s really helpful.
Workaround: when the keyboard stops working, press Escape or Cmd+1. That should bring focus back to the editor. If that doesn’t help: Cmd+Shift+P > Developer: Reload Window.
The team is aware of the issue, and your report with exact repro steps will help with prioritization.
Thank you Dean for the info. Up till now I didn’t encounter the problem again, should it trigger I will surely let you know if the workaround works.
Keep up the good work!
Best,
I’m still seeing this exact behavior. Started up a localhost dev server, then the Cursor browser opens and the keyboard bindings get stuck. Reload Window does restore normal behavior, but neither Esc or Cmd+1 fix it.
I also did not see the “skipping keybinding dispatch…” log in the dev tools, so that may not be the entire issue.
This issue has been fixed in a recent Cursor update. Updating to the latest version should resolve this. If you’re still experiencing this on the latest version of Cursor, please raise a new thread and we’ll take a look.