in plan mode when typing in the chat box the up key/arrow does not work. down, left and right arrows work but up arrow never works. this was the case since cursor ai plan mode was introduced a few month ago and was never fixed.
Steps to Reproduce
open plan mode and type a few words. then try to press the up key. it never works.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
yes! I hated this issue
I always be in a hurry so I just press the left arrow with ctrl to skip words
even the “home” button does not take me to the start of the prompt input!
this has been an issue from a long time
Hi, sorry for the late reply. Here are the answers:
Does the Up arrow work in normal Chat mode (not Plan mode)?
yes, but as soon as one switches to any other mode (agent, plan, bug, ask), then the up arrow does not work in any of the modes.
Do you have any custom keybindings for the Up arrow? (Check Cursor Settings > Keyboard Shortcuts, search for “up”)
It looks like workbench. there are a whole bunch of shortkeys with t
he uparrow attached.
-Can you reproduce this in a new empty project?
No, when I created a new empty project it did not happen. that is the `uparrow` is working as intended when I switch between modes. but i did not have any file folders or content. so that is strange.
Thanks for the detailed reply. Really helpful, and the fact that the bug doesn’t reproduce in a new empty project narrows it down a lot.
From your keybindings screenshots, everything looks standard. Let’s figure out what in your main project is triggering the bug:
Open Help > Toggle Developer Tools, then go to the Console tab. Try to reproduce the bug with the Up arrow in Plan mode. Do you see any errors or warnings in the console?
Check extensions: Command Palette Ctrl + Shift + P > Extensions: Show Installed Extensions. Do you have anything custom installed besides the defaults? You can also try opening your project with cursor --disable-extensions and see if the bug still reproduces.
Let me know what you see in the console and which extensions you have. That should help narrow down what’s causing it in this project.