Request ID: ed10bdc1-49a6-4e2f-993f-e5b43e38efd2
[failed_precondition] Cloud plugin slash commands could not be resolved for this followup. Refresh them and try again.
Cloud plugin slash commands could not be resolved for this followup. Refresh them and try again.
ConnectError: [failed_precondition] Cloud plugin slash commands could not be resolved for this followup. Refresh them and try again.
at e (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:12725:483311)
at async Object.addAsyncFollowupBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:7998:55174)
at async kln._sendFollowupRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9346:67336)
at async kln._submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9346:65057)
at async kln._submitMessageForAgent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9345:154671)
at async qNm.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9339:5102)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:16869:172569
Hey, thanks for the report and for sharing the full error text with the Request ID, that really helps.
The Cloud plugin slash commands could not be resolved for this followup error means the plugin slash commands, in your case from Superpowers, didn’t resolve on a follow-up message inside the cloud agent. A couple workarounds while we look into it:
Instead of using the slash /requesting-code-review, try writing it out in words, like “use the requesting-code-review skill”. On follow-ups, this usually avoids the slash command resolver.
Or start a new agent instead of sending a follow-up in the old one. On the first message, commands are fetched fresh.
A couple quick questions so we can dig deeper:
Does the same thing happen if you run the agent from cursor.com/agents on the web, not from the Agent Window in the desktop app?
Does it fail every time, or does it sometimes work?
Does the same thing happen if you run the agent from cursor.com/agents on the web, not from the Agent Window in the desktop app?
Actually it’s done from the cloud agents, instead of the local machine. I just checked on my cursor mobile app, I don’t see the same skill appeared there at all. When checking agents window, it’s definitely there. But the weird thing is it always works fine in my other personal repos.
Just not this particular repo for some strange reason…
Glad the workaround removed the error. But one thing to note: based on the screenshot, the skill didn’t actually run. The agent said “The requesting-code-review skill isn’t in this environment” and did a generic Bugbot-style review instead of the Superpowers skill. So the error is gone, but requesting-code-review from Superpowers still isn’t working in this environment.
And that matches what you noticed: in the Agents window the skill is visible, but in the cloud environment for this specific repo it’s not there. That’s why it doesn’t show on mobile either, while other repos are fine. It looks like the plugin isn’t getting materialized in the cloud environment for this repository.
To dig deeper, a couple questions about this repo:
Is it under the same GitHub account as the repos where everything works, or under a different org or account? Is it private?
If you open a new cloud agent on this repo and in the very first message type /requesting-code-review, does the skill show up in the slash menu and run, or do you still get “isn’t in this environment”?
This will help figure out whether it’s a provisioning issue for this repo or something else. Let me know.
