Text after custom commands in Cursor CLI is ignored / cut off

[ThomSMG (Thom)]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Text after custom commands in Cursor CLI is ignored / cut off.
Mostly the text after the command serves as it’s input. However, in Cursor CLI, since this part is cut off, I can not reference to it in the command’s instructions.

Steps to Reproduce

Add a command to ~/.cursor/commands/echo.md

Echo back the input you were given.

Run the command e.g. /echo Hello World

Expected Behavior

Should echo back “Hello world” as in Cursor Editor.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2025.11.06-8fe8a63

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. There’s currently a bug where arguments after the command are ignored. For example, /echo Hello World will process only /echo and the text “Hello World” will be lost. In Cursor Editor this works correctly.

This bug is already being investigated by the team.

[dryekindrew (Primož Verdnik)]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Currently, it is possible to execute slash commands in the CLI agent only without parameters. If a parameter is specified, it’s deleted and ignored.

Steps to Reproduce

Type in a slash command followed by a space and a parameter (any word basically)

Expected Behavior

One would expect that the subsequent words would be interpreted as a parameter exactly as it is in the Cursor IDE version.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

2025.11.25-d5b3271

Does this stop you from using Cursor

No - Cursor works, but with this issue