Typescript code actions (like Extract Constants, Functions, Move to File) no longer works with the error message “Actual command not found, wanted to execute _typescript.didApplyRefactoring /3255”
Steps to Reproduce
Create a minimal TypeScript project
Execute code actions (e.g. Extract Constants)
See it failed with error message
Expected Behavior
The code action fails with “Actual command not found, wanted to execute _typescript.didApplyRefactoring /3255”
The last number varies depending on the action
Hey, thanks for the detailed report with the version and screenshot. The Actual command not found, wanted to execute _typescript.didApplyRefactoring error is really clear.
This is a known issue we’re tracking. It affects code actions from extensions in general, not just TypeScript. Users reported the same symptoms for Dart, ESLint, and others. It’s tied to changes in recent stable builds. It started in 3.14.21+, so your 3.15.6 is affected too. This isn’t anything in your setup.
A workaround that helps right now is downgrading to 3.14.7 or below. The issue doesn’t happen there. For TS refactorings like Extract Constant/Function and Move to File, there isn’t an alternative via the command palette, so a downgrade is the most reliable option if these actions are critical for your work.
Also experiencing this issue with ESLint quick fixes. Oddly enough, sometimes it works, sometimes it doesn’t. I think it only works if the rule disabling/fixing is a rule built into ESLint.
Hey @insraq, quick update on the remaining code actions crashes.
The original errors for Extract Constant/Function and Move to File are already fixed in the latest stable version, so if you haven’t updated yet, it’s worth doing that now.
The remaining cases like Add Missing Imports and extension quick fixes that crash after the first run are fixed in Cursor 3.19, so please try again once you’ve updated to that.
Until then, the reliable workarounds are to apply the fix via the right-click menu, Command Palette, or the Quick Fix link in the hover tooltip.
cc @Oliver_Yasuna, the ESLint quick fixes are in the same bucket, so this affects you too.