Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Not sure if this is a bug or a gap, but it feels like I should be able to run Bugbot from cloud agents that Grok Bot creates.
Docs say /review and /review-bugbot are available in Cursor 3.7+ and at cursor.com/agents. High effort exists in the Bugbot dashboard. I expected a cloud agent started from Grok Bot to have that same skill, so I could say “review this PR with Bugbot, high effort, fix findings, loop” without a GitHub bugbot run comment and without sitting in the Agents UI / menu.
That is not what happens.
What I did
Repo: private
From Grok Bot I launched (and later replied to) several Cursor cloud agents, one per existing PR. Each agent was told, in the launch/follow-up prompt:
Stay on the existing PR/branch. Do not open a new PR.
Run Bugbot in this session via /review or /review-bugbot vs the PR base (usually main).
Use high effort if the skill accepts it.
Do not comment bugbot run / cursor review on GitHub.
If the skill is missing, stop and list the skills you actually have. Do not fake a “Bugbot-style” self-review.
I also tried the GitHub comment trigger earlier (bugbot run on the PR). That does not start Bugbot on this repo, which is why I wanted the in-session skill.
What happened
Nine separate cloud agents, same result.
They looked at:
MCP tools (search for “review” hits PostHog review-queue tools, not Bugbot)
~/.cursor/skills-cursor (env-setup, migrate-to-builds, subscribe, canvas)
Installed plugin skills (Cloudflare, Stripe, Neon, PostHog)
Native tools in the session: CreateGoal, GenerateImage, UpdateGoal
There is a cursor-guide subagent that can answer product questions about Bugbot. That is not the review skill.
/review-bugbot and /review are not in the skill list. The agents stopped as instructed. They did not run real Bugbot. They could not attach the skill from inside the session.
Several of them said the only way to run it is for a human to open the agent page and pick /review-bugbot from the / menu in that chat, e.g.:
/review-bugbot compare against main
Grok Bot’s CloudAgent reply cannot type that slash command for them. So from Grok Bot I can start the agent, give it the PR, have it fix code, but I cannot actually start Bugbot.
Why this is frustrating
The loop I want is:
Grok Bot → cloud agent on an existing PR → real Bugbot (high effort) in that session → fix → re-run → report.
What I get instead:
Grok Bot → cloud agent that reviews itself unless I remember to forbid that → or an agent that correctly says “skill missing” → I still have to open cursor.com/agents and / the skill by hand, once per agent.
If the product intent is “Bugbot in the agent,” Grok Bot–created cloud agents should get the same /review-bugbot skill as agents I start from the Agents UI. If the intent is “only from the / menu,” the docs should say that cloud agents launched from Grok Bot / the CloudAgent API do not include it, and Grok Bot should be able to attach or invoke that skill on reply.
High effort is the other half: I want Bugbot High, not a coding agent pretending to be Bugbot. That only matters if the real skill is actually there.
Actual (2026-08-31): skill not attached. MCP “review” search is PostHog. Agent asks you to pick /review-bugbot from the / menu on https://cursor.com/agents/.
Happy to share more agent IDs or transcripts if useful.
Steps to Reproduce
From Grok Bot, launch a Cursor cloud agent on a connected GitHub repo (CloudAgent launch, existing repo, existing branch/PR).
Follow up: “Run /review-bugbot in this session at high effort vs main. If the skill is missing, stop and list your skills. Do not comment on the PR.”
Read the agent report.
Expected Behavior
from current docs: the agent invokes /review-bugbot / /review.
Screenshots / Screen Recordings
Operating System
Linux
Version Information
Date: 2026-08-31
Client: Grok Bot (Cursor desktop assistant) launching cloud agents
Cloud agents: Cursor-managed VMs, cursor.com/agents/bc-…
Repo: GitHub clientup-group/clientup (private)
Bugbot GitHub comment trigger on that repo also does not run (separate, maybe Automations / install)
For AI issues: which model did you use?
grok 4.6 high
For AI issues: add Request ID with privacy disabled
Example agent: https://cursor.com/agents/bc-50a353b8-41f1-4b84-8f67-1a617d8a77e2
Does this stop you from using Cursor
No - Cursor works, but with this issue
