Cursor CLI: /commands, models, ctrl+d

Ideas Feature Requests
1

Feature request for product/service

Cursor CLI

Describe the request

Cursor CLI requests:

  • One accidental ctrl+d press instantly quits - if you were working on a long prompt it’s gone (ctrl+d is supposed to delete one char with normal emacs bindings, so it’s easy to accidentally press it - Claude Code and Gemini CLI require two consecutive ctrl+d presses to quit, as a guard)

  • Can’t use my custom /commands from ./cursor/commands like you can in the IDE

  • Support for more models (I know this gets asked all the time and is coming soon, but I would be using gpt-5-high, grok-4, and gemini-2.5-pro)

  • Are cursor-agent line edit counts included in the Cursor web dashboard?

  • Vim keybinding support is rudimentary (no e.g. f or F to move forward/backward by char, etc)

  • Curses UI gets laggy with long prompts, I have to type slowly or else it drops characters

  • Custom hooks on e.g. complete would be nice (Claude Code has this) so I can add code that sends me a notification. I’ve built a hacky solution in tmux that works for me (GitHub - dnielbowen/cursor-notifier: Sends a Discord notification when Cursor CLI agent instances go idle) but it would be more robust with a hook

Overall, though: Cursor CLI is more great work from the incredibly cracked Cursor team, thanks.

2

Another one:

  • A one-liner command like below is nice (fast and easy for commit messages for example) but the auto model often hangs, does not quit (occasionally does). It does reliably quit when using e.g. --model gpt-5.
    • echo "commit" | cursor-agent -fp --output-format text --model auto
3

Please make cursor-agent require two Ctrl-D presses to quit, since a single accidental C-d (delete-char in Emacs) currently kills the whole session.

4

A fix for ctrl-d is critical.

5

Two ctrl+d presses globally would be a step forward, though ideal behavior in my opinion would be for it to emacs-style delete a char if the prompt is non-empty (this would match other supported emacs editing shortcuts) and if the prompt is empty, then either one or two ctrl+d presses could exit (one is fine in this no-prompt case since you can resume the last session if exiting was accidental - it’s also similar to how one ctrl+d on an empty shell exits. It’s the no-warning dumping of the current prompt that’s the imminent issue to me.