Custom commands do not support prompt intellisense consitently

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’ve become a die-hard fan of custom commands for inngest. For many tasks that I was relying on rules for, commands are a much better fit. Loving them. There is a consistent issue, however, that seemed to crop up early on and has now been largely persistent since it did: They lack consistent intellisense (or perhaps called autocomplete) support in the prompt input.

When I first created my original couple of custom commands, I was getting intellisense-like behavior, where I could type my commands and I’d see them in the popup so I could select them. Then even after initially inputting hte command, even my “parameters” were also supported (many of my commands support an environment parameter, like dev or staging). This was great and allowed rapid use of my commands with high accuracy.

After the first few times I used my commands, however, this intellisense/autocomplete support simply stopped. I do not see any of my commands in the command palette that pops up when I type / and I no longer have any support for param autocompletion or anything like that. I don’t know why it stopped, however, outside of the very rare case, it seems to have stopped completely.

At the very least, we need the command palette to work. Having the autocomplete for parameters was also really useful as it improved precision in using the commands.

Steps to Reproduce

  1. Create a custom command (preferably with one or more “parameters”)
  2. Execute your command in a few prompts (should see intellisense/autocomplete behavior)
  3. Keep executing your command (after the first several, three maybe four uses) and watch intellisense/autocomplete support vanish, and commands no longer listed in palette.
  4. Weep.

Expected Behavior

  1. All commands show up in custom command palette during autocompletion in prompt.
  2. Parameters support autocompletion as well.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.52
VSCode Version: 1.99.3
Commit: 9675251a06b1314d50ff34b0cbe5109b78f848c0
Date: 2025-10-17T01:41:03.967Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

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