Cant type characters but can delete or ctrl+z into the editor page

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The editor area will not accept any characters, i can delete characters and ctrl+z.

Steps to Reproduce

Open the editor page via going there from review page, try to edit the line

Expected Behavior

It should just work

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.11.18 (user setup)
VS Code Extension API: 1.125.0
Commit: a1d1c20f31cb834d7d50581e6da017d2b822e380
Date: 2026-07-11T21:40:27.094Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report and the video, you described the issue really well. If Delete and Ctrl+Z work but typing doesn’t, it usually means the editor is losing input focus when switching from Review back to the file.

To narrow it down, can you check a couple things next time it happens:

  1. Switch to another tab and back to the file, does typing start working again?
  2. Reopen the file close and reopen the tab, does that help?
  3. Open the same file in a normal Editor window using Ctrl+Shift+N, can you type there normally?

Let me know which of these brings typing back. It’ll help us figure out where focus breaks and reproduce it on our side.

1 - Failed

2 - Failed

3 - Works

Bump

Thanks for checking, that really narrows it down. Since method 3 worked but the first two didn’t, it looks like the input gets stuck specifically in the editor inside the Agent Window when switching from Review, and the normal editor window isn’t affected.

As a temporary workaround, open the file in a normal Editor window using Ctrl+Shift+N, typing should work fine there. You can also try switching to the classic layout if the Agent Window isn’t critical for you.

I’ve reported the bug internally with your debug results, they’ll help us reproduce it on our side. I can’t share an exact ETA for a fix yet, but I’ll post an update in the thread as soon as I have one.