I cannot type spaces in Cursor’s integrated terminal at all.
The space key does not insert any character in the terminal, no matter what. Letters, numbers, and other input work, and spaces work normally in Cursor chat as well as in external terminals outside Cursor. The issue appears to be isolated to the integrated terminal inside Cursor.
This makes normal shell usage very difficult because I cannot type commands that contain spaces (for example git status, cd my folder, echo hello world, etc.) unless I paste spaces manually.
Steps to Reproduce
Open Cursor on macOS.
Open any workspace/project.
Open the integrated terminal.
Try typing a command that contains spaces, for example:
git status
echo hello world
cd Some Folder
Press the space bar between words.
Expected Behavior
Pressing the space bar in the integrated terminal should insert a normal space character, just like in external terminals and other text inputs in Cursor.
Additional Notes
Spaces work in Cursor chat.
Spaces work in external terminals outside Cursor.
The issue seems specific to Cursor’s integrated terminal.
I am on a MacBook Pro 14-inch (Nov 2024), M4 Pro, 24 GB RAM.
Operating System
macOS 26.4 (25E246)
OS: Darwin arm64 25.4.0
There was an older macOS bug report mentioning that the spacebar did not work in Cursor, which may be related: Debugging typing not working
I went into Cursor Settings → Beta and left the Glass Preview. This downloaded (after a short wait) the Default build (not Nightly) and restarting Cursor restored the spaces in the terminal.
Well, after reverting back to Default build, my chat history is gone. But, if I switch back to Nightly, it is there. So, I guess the choice is: spaces in terminal OR chat history.
ok I may have to retract my last statement.
This morning capital letters was working in terminal just fine in Cursor ( was on the latest build as well), but I just opened a new terminal and suddenly they (capital letters) no longer work.
Hasnt been a breaker for an productivity, but still….it is an odd one.
About the new uppercase or Shift issue in the terminal, the team knows about it. It’s probably a related regression from the same keybinding refactor. No ETA yet, but your reports here help us prioritize it.
If you’re seeing the uppercase issue, can you confirm which build you’re on? Check Help > About or run Cursor: About from the command palette. We want to make sure we’re tracking the right version.
Just tried again, and can confirm it is still not working. No idea how I had it working earlier this morning at start of my session, but oh well.
Here is hte build info
Version: 2.7.0-pre.177.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: 6f2d8c84cbe9db9bb5ebb53a2aee4c0110851b50
Date: 2026-04-01T16:48:21.497Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0
disregard the above. I just saw therre was an update available. I updated and now uppercase (Shift) works just fine again.
Here is build info of working build
