Thanks for digging into the console. The Failed to parse project hooks configuration undefined error looks like a regression in Marketplace plugin hook config parsing in 3.0.12. To confirm it and file an issue, I need a couple more things:
In Developer Tools > Console, click the error line and expand the stack trace. Send a screenshot or paste the full text. Lines before and after help too.
If your current workspace has a local .cursor/hooks.json, check whether hooks from it show up in Settings > Hooks. This helps confirm if the problem is only with plugin hooks or the whole hook loader.
Try Settings > Hooks with a different project open, or with no folder open. Do the plugin hooks appear?
Quick workaround: in Settings, find Continual Learning, turn it off, run Cmd+Shift+P > Reload Window, then turn it back on. This sometimes triggers a re-init.
If it reproduces in a clean workspace, it’s most likely a bug on our side and I’ll file a ticket.
same error here. plugin hook is not installed. tried everything you said above. no error in hooks output it just says
[2026-05-04T14:48:40.003Z] No user hooks configuration found
it does find my project level hook but not plugin level that i installed just for myself. i am too trying to use continues learning plugin
Thanks for confirming, so it’s not an isolated case. To match it with the OP’s report, can you share a couple details:
Cursor version Cursor Settings > About or Cursor > About Cursor and your OS.
Open Developer Tools > Console via Cmd+Shift+P then Developer: Toggle Developer Tools, go to the Console tab, and check if you see [HOOKS] Failed to parse project hooks configuration undefined or something similar. If you do, expand the stack trace and share a screenshot or the text.
Was the plugin installed from the public Marketplace, or from a local or team marketplace?
Quick workaround to try. In Cursor Settings find Continual Learning, turn it off, then Cmd+Shift+P > Reload Window, then turn it back on. Do hooks show up after that?
In parallel, I’ll log this as a bug on our side. No ETA yet, but I’ll post in the thread if there’s an update.
Thanks @da1z and @Jason_DAmour for confirming and for the stack trace. The issue is consistent: marketplace plugin hooks silently don’t register on macOS. On init, the console shows [HOOKS] Failed to parse project hooks configuration undefined, while the skills and rules from the same plugin load fine. It reproduces in an empty workspace, so this isn’t related to any project-level config.
If anyone finds a reliable workaround, please share it here and I’ll add it to the ticket. Things we already tried that didn’t help: toggling the plugin off and on, then Reload Window.
I also run into this Problem.
Activating the settings “Include third-party Plugins, Skills, and other configs” is my current bypass. However this is a user-facing action and it is not a valid solution for my use case where I distribute the plugin internally.
Hey @Thomas_PELLETIER, thanks for confirming and for the workaround. It’s good to know the Include third-party Plugins, Skills, and other configs toggle gets around the issue. I agree it’s not a real fix for internal distribution since it requires action from each user.
We’re tracking the bug on our side, it’s the same [HOOKS] Failed to parse project hooks configuration undefined as others in the thread. No ETA for a fix yet, but we’ll post an update here as soon as we have one.
If the plugin is distributed via the team marketplace, let me know. That’ll help us confirm the scope.
Hey @Jason_DAmour, thanks for reproducing this with local plugins from ~/.cursor/plugins/local/ too. That’s an important signal and it means the issue is broader than just the marketplace. I’ll add this detail to the ticket, so the scope is bigger than we first thought.
We’re still tracking the bug on our side and there’s no ETA yet. As soon as we have an update on a fix, we’ll reply here.
If another user finds this thread later, a temporary workaround is to enable Include third-party Plugins, Skills, and other configs in settings. Thanks @Thomas_PELLETIER. I know this isn’t a solution for internal distribution since it requires each user to do it manually.