Cursor CLI command incorrectly handles paths with spaces

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

The cursor CLI command no longer properly handles file paths containing spaces. It used to work fine with v1.6, but now it doesn’t work correctly with any version.

Steps to Reproduce

$ cursor ~/my\ project/

Expected Behavior

Cursor should open with a single folder: my project

Actual Behavior

Cursor opens with two files:

  • An empty file named my
  • An empty file named project

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Additional Information

I reported a bug when v1.7 was released, but it still hasn’t been fixed. I’m really having trouble editing Git commit messages with Cursor in a folder includes spaces.

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. I’ll pass it on to the team.

5

Hey is there any update on this?

It’s been a while and there are multiple bug reports related to this issue

I have to open a whole other app every time I need to write/edit a commit message which is a bit annoying :confused:

1 Like
6

Hi, is there any update about this issue?

7

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.