Specific context: Arch Linux, Cursor CLI (v2025.11.06) ran in Neovim 0.11.5 integrated terminal (specifically the Sidekick.nvim plugin)
Using Cursor CLI interactively for agentic work on my local repo, I faced two problems:
The input field keeps pushing my cursor back to the end of line when i try to input a character somewhere else than the end of the line. I can only add one character at a time or I have to erase half of my prompt to rewrite everything. Very annoying.
Encountered an infinite command run task in the CLI with Composer1 running a long-running python script, unfortunately I couldn’t stop the process with Ctrl+c, it was locked there. I had to kill the entire cursor-agent process to actually get rid of it, reopening it, finding back the conv, and continuing without asking to run the script (after reproducing the bug a second time).
Other than this specific python script running and freezing everything, i was still able to use Ctrl+c to stop other tasks, like thinking, web searches, etc. Just running this python script froze everything. When i tried Gemini CLI after, no such problems, the input field worked as expected and the script ran normally.
Steps to Reproduce
First bug: try to write a long prompt, then try to go back and change some characters previously written, while the bug is occuring, the cursor will be forced at the end of the prompt after every character typed “in the middle” of the prompt.
Second bug: ask Composer1 to run a long-running python script (that keeps running without an exit i guess), and try to use Ctrl+c to stop it.
Expected Behavior
First Bug: I should be able to modify parts of the prompt I’ve already written without my cursor being pushed back at every character typed.
Second Bug: Ctrl+c should also stop the long-running commands, not only the “thinking” tasks, web searches, etc.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. Both issues you described look like new bugs in the Cursor CLI.
For the “jumping” input cursor: please test whether this also happens in a standard terminal (outside Neovim). This will help determine if it’s a Neovim/Sidekick.nvim compatibility issue or a broader CLI bug. If possible, share your $TERM value.
For the long‑running script freeze: there’s already a related report about CLI freezes/hangs during long sessions, and it’s been escalated. Your case where Ctrl+C doesn’t stop the Python script matches similar symptoms.
I’ll escalate both issues to the development team. Please also share:
Does the “jumping” cursor occur with simple short inputs, or only with longer prompts?
What makes your Python script “long‑running” (continuous output, no exit condition, etc.)?
Let me know if the issues reproduce in a standard terminal.
For the jumping input cursor bug : yes i’ve been able to reproduce the bug with two terminals, alacritty 0.16.1 and Ghostty 1.2.3-arch2. The jumping happens in both, whatever the length of the prompt, with short and long prompts the same. When I type one character (space or letter or punctuation) in the middle of the prompt my cursor is jumped at the end of the prompt.
For the long-running script freeze: i also reproduced the freeze on both Ghostty and Alacritty terminals. For the specificities of the long-running script: this is a script mixing twitchio (Twitch Chat API) and calling a shell script which connects through SSH to another machine on my network, and most importantly, it’s asking for the SSH password on first run. I think this SSH password step is the culprit. Asking the cursor-agent to run the shell script directly with the password to input also froze it the same way. After running the script manually, inputting the password correctly, and going back to cursor-agent, and asking it to run again, since the SSH password has been recently entered, it did not require it again, and the script ran through the CLI agent WITHOUT freezing this time! I could stop the process with Ctrl+c normally here. So yeah, to reproduce this bug on your part, I would suggest making the CLI agent run a shell script that connects with SSH to another machine and asking for a password. The CLI agent should freeze at this SSH password step, and Ctrl+c to stop the task should not work here.
@deanrie I’m also seeing both issues, and have a recording of the input issue ( the freezing issue isn’t really feasible to record since it’s just the cli frozen and failing to accept any input, including termination hotkeys )
What’s the guidance for downgrading in the meantime? This effectively breaks usage of the CLI for affected users, and I haven’t seen and ETA on corrective measures either, two(?) weeks after release
Found a fix: in ~/.local/share/cursor-agent/versions/2025.11.20-a4d3945/, search for }, [cursorToEndSignal, valueProp]); and remove valueProp from the dependency array.
The issue seems to be that valueProp is included in the useLayoutEffect dependency array, which causes the effect to fire on every keystroke and reset the cursor position to the end.
