Hey, thanks for the detailed report. This is a known issue with the code action menu opened from the keyboard using Cmd+Enter or Alt+Enter. When you pick an item, the extension command doesn’t resolve and you get an error like Actual command not found. It’s not just cSpell. We’re seeing the same thing with TS, C#, Dart, and other extensions.
Good news, the fix is already done and will be included in an upcoming release. It’s not in 3.15.6 yet. I can’t share an exact date, but I’ll reply here once the update is out.
For now, the workaround is to use the right click context menu like you noticed. It goes through a different path and isn’t affected by this issue.
Hey @gregorywhale, thanks for coming back with details, that’s an important clarification.
You’re right. What shipped in 3.16 was only part of the fix. The symptom you described, after reload the first QuickFix works and the next ones fail again with Actual command not found, and the case with imports via rust-analyzer.resolveCodeAction have the same root cause. The second part of the fix is already done and will ship in Cursor 3.19. It’s not in stable 3.17.19 or 3.18 yet, so updating to the current stable won’t remove the remaining symptom. You specifically need 3.19.
Once 3.19 is out, please try again. No need to open a separate ticket, this case is already covered. Until then, the existing workaround still works, use the right-click context menu. It goes through a different path and isn’t affected.
The workaround you are suggesting is not really an option in daily work. Developers work fast and mostly with the keyboard. You do not spend time right-clicking on every issue or opening the command palette and typing the fix. None of this is a quick or feasible solution.
This is a blocker.
Hey, you’re right. For keyboard-driven work, having to right-click every fix isn’t a solution, it’s a hack. Totally agree.
The good news is you won’t need a workaround forever. The real fix for the exact scenario you described after reload the first Quick Fix works, but the next ones fail with Actual command not found, including imports is already done and will ship in Cursor 3.19. It’s not in 3.17.19 or 3.18, so updating to the current stable won’t fix it. You specifically need 3.19.
I can’t share an exact date for when 3.19 will hit stable yet, but I’ll reply right here as soon as it’s available so you can test your exact case without opening a separate ticket.
Until then, if you need a one-off workaround, Reload Window resets the state, and the first Quick Fix after reload works from the keyboard again. I know that’s not a real long-term option, it’s just a temporary escape hatch if you’re blocked.
Hey, thanks for the workaround, @Brad228. For users who are stuck waiting for the fix release, this really helps.
A couple notes for anyone else who wants to use it, since this edits the extension file itself extension.cjs:
When you update cSpell, the file will get overwritten, so you’ll need to reapply the patch.
Before replacing anything, compare it with the original file like Brad suggests and make sure you understand what’s changing. You should only replace extension files from attachments if you’re doing it on purpose and you know what you’re changing.
Basically, the change registers a fresh wrapper command for each code action. That way, calling the command no longer depends on the set that gets reset when you open the menu using the keyboard. That’s why the Actual command not found error goes away.
About a permanent fix. The second part of the fix on our side is ready and will ship in Cursor 3.19. It’s not in 3.17.19 or 3.18 yet, so updating to the current stable won’t remove the remaining symptom. Once 3.19 reaches stable, I’ll reply here so you can test your setup without the patch.