[composerModesService] Failed to register action for mode

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

  • When I try to start using Cursor as usual, this popup suddenly shows and chat pane became disable under specific project.

Steps to Reproduce

Still investigating but seems like if you have issue in the previous conversation, this bug could occur

Expected Behavior

Be able to change mode and have conversation

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.33
VSCode Version: 1.99.3
Commit: a84f941711ad680a635c8a3456002833186c4840
Date: 2025-10-03T03:28:06.574Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Same issue found but not resolved

I found a rough solution.

under the projects you are having the issue, run below command

grep -RIl --include=workspace.json -e “"folder": *"file://$(pwd)"” ~/Library/Application\ Support/Cursor/User/workspaceStorage

and you can get some dir path like below.

Users/hoge/Library/Application Support/Cursor/User/workspaceStorage/64358cb4269c7880f60ecc9e3c70f2f6/workspace.json

And you can simply remove this folder

sudo rm -r Users/hoge/Library/Application Support/Cursor/User/workspaceStorage/64358cb4269c7880f60ecc9e3c70f2f6

Then your cursor would start working again however you lost conversation history in that project.

I have same problem, the “rough” solution didn’t help

Same issue here, and the rough solution didn’t work either
This is a major bug, please solve this asap

Same issue here. Unable to use cursor in any of my workspaces. I can’t afford to lose chat history. There is too much context there.

Also same issue when I start a new chat

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

First I found out cmd+I doesn’t work any more after the update.
When I try to close the chat or create a new one via the Command Palette,
I get errors like:

Command 'Cursor: New Chat' resulted in an error
composerModesService] Failed to register action for mode 54f7775e-bb21-4ed2-a50b-387c3e78ecaa:

Unable to use Chat console at all.

Steps to Reproduce

See above

Expected Behavior

cmd+i works as before. Chat interface works.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.38 (Universal)
VSCode Version: 1.99.3
Commit: fe5d1728063e86edeeda5bebd2c8e14bf4d0f960
Date: 2025-10-06T18:18:58.523Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

Yes - Cursor is unusable

I can’t close the chat panel, and the folder panel has moved to the right. Even most of the buttons can’t be clicked. The last update is a mess…..

I downgraded to 1.6 but still encounter the same issue. Maybe it’s not related to the update but some other reason.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m experiencing an issue making cursor unusable, where Send button in the chat doesn’t work — clicking it does nothing. I also get an error message with "[composerModesService] Failed to register action for… " , i tried switching models but that also doesn’t work,

i’m using cursor 1.7.38. Restarting Cursor and killing the process didn’t resolve it.

anyone seeing this issue ? is there a workaround

Steps to Reproduce

  • On cursor 1.7.38
  • open cursor
  • open chat , type something
  • clicking send (to send the prompt) doesn’t work

Expected Behavior

  • prompt to be sent and agent responds

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Current Version: 1.7.38

For AI issues: which model did you use?

happens with any model

Does this stop you from using Cursor

Yes - Cursor is unusable

I had to completely delete cursor including $HOME/Library/Application Support/Cursor and $HOME/.cursor folders. Then installed it fresh. It then started working for me.

Also hitting this bug on Version: 1.7.39 and it makes cursor unusable.

Hey, thanks everyone. We’re already looking into this.

2 Likes

Important : on my side, disabling the Plan mode > Reload window made Cursor work again

image

image

8 Likes

confirming that this resolved the issue for me as well.

If you have a hard time finding plan mode it’s in Cursor Settings → Beta → Plan Mode

1 Like

I also have this issue unfortunately.

A workaround is to downgrade to v1.6 and reload the cursor window (CMD + P) >Developer: Reload Window.

100% it’s Plan Mode. I had the popup - Do you want to try plan mode? I clicked yes and the problem started. Then I turned it off in settings and restarted cursor and it went back to normal.

SOLUTION:
I’ve also got hit with this issue after a recent update. Disabling Plan Mode in Beta worked, but it did not seem like a proper solution. So after some tinkering the issue actually was that I had my own custom “Plan” mode created awhile ago. Apparently, it was conflicting with the new Cursor’s Plan mode simply by name. This caused registration error resulting in empty mode list and inability to use Cursor. After I removed my custom Plan mode - the Cursor’s own Plan mode registered successfully and the error was gone (and I can now use Cursor’s Plan mode too which is great by the way) Hope this helps!

3 Likes

Hey, thanks for the info, that’s very helpful. We’ll look into it.

1 Like

Can confirm this issue was because of the custom Plan mode that I’ve created as per Cursor’s previous docs. In order to remove it, I had to first disable Plan mode from Cursor Settings → Beta, delete my own custom Plan mode and then reenable Cursor’s beta plan mode

2 Likes