Title: Official connector so Grok Bots can send briefs directly to Cursor agents (and receive reports back)
Body:
Currently I use Grok Bots (e.g. Chief of Staff and QA) to plan, track compliance, and generate detailed briefs for site work. Those briefs then have to be manually copied into Cursor so an agent can execute them and the results have to be manually pasted back.
A first-party connector (or MCP/API surface) that lets a Grok Bot:
hand a structured brief directly to a Cursor agent (cloud or local),
receive the agent’s report / commit / check results automatically, and
keep the conversation context on both sides
would remove me from the middle of the loop. Shared account, plugins, and computer already exist; this feels like the natural next step for agent-to-agent handoff.
Vote / use-case: anyone running multi-bot workflows that include coding or deployment tasks.
Most of this already exists. Every Grok Bot has a built-in Cursor connection: it can launch a Cursor cloud agent with a brief it wrote, gets woken up automatically when the agent finishes with its report, transcript and branch or PR, and can send follow-ups to that same agent so the context carries over.
Try telling your QA or Chief of Staff bot something like “launch a Cursor cloud agent on with this brief and report back when it’s done”. If you have a saved Cloud Agents environment, you can name it instead of a repo.
To run the work on your own computer rather than a Cursor VM, start a worker there with agent worker start (setup is in the My Machines docs, Windows included) and ask the bot to launch on that machine by name.
One heads-up: if a routine launches the agent, the bot’s main chat may not be able to follow up on it yet. That’s a known issue the team is aware of.