TL;DR
- A Grok Bot can hand coding work to a Cursor Cloud Agent, which works on a separate computer and can open a pull request.
- Since September 18, a Bot can also start a Project: a Cloud Agent that plans the work and runs its own agents. It's built for bigger jobs.
- Stopping a Bot also stops the other Bots it handed work to and the Cloud Agents it started (since September 17).
- You connect GitHub, GitLab, Bitbucket or Azure DevOps once, and the Bot can then manage PRs: reviews, branches, labels and releases.
- On a team, admins control this with the Cloud Agents switch. It's on by default.
On September 30, the official Grok Bot account announced that Bots are "now more powerful for building software." Three things changed:
- Bots can hand off coding tasks to Cursor.
- Bots can manage your pull requests with the GitHub and Origin plugins.
- Bots can share video demos of what they build.
We touched on this in our week in review. This note goes further: what the official docs now say, and what it means if you build things with Bots.
What the docs confirm
The handoff goes to Cursor Cloud Agents, a kind of coding agent. The Teams and enterprises guide says Grok Bot "can delegate coding tasks to separate computers" under your existing Cloud Agent controls. It also lists a Cloud Agents switch for team admins:

Two details matter here. The switch is on by default and applies to the whole team. And delegated work runs on separate computers, not on the shared computer your Bots normally use.
The GitHub and Origin side runs through plugins. The Computer and apps guide explains that connectors are installed as plugins from Connect Apps, then attached to a task by typing @ in chat:

We didn't find a docs page that names the GitHub or Origin plugins, or that covers video demos. For those, the announcement is the source for now.
What it means for a builder
Without a handoff, a Bot that writes code does it on the shared computer all your Bots use. Now your Bot can stay the planner and pass the actual coding to Cursor. The finished change comes back as a pull request that your Bot can track.
In plain words:
- Your Bot can coordinate, Cursor can code. Ask for an outcome ("add a contact form to the site"), and the Bot can hand the coding to Cursor.
- Changes arrive as PRs. A PR is a proposed change you can look at before it goes in. Read what changed, try the preview if there is one, and only then merge.
- Plugins are account-wide. Once you add the GitHub or Origin plugin, every one of your Bots can use it. Give it access only to the repositories you want Bots working in.
- Teams can switch it off. If you're on a team and don't want Bots delegating code, an admin can turn off the Cloud Agents control.
Others are already working this way
Federico Viticci of MacStories described his setup on October 2. His Primary Bot starts group threads with specialist Bots, and those Bots start Cursor cloud agents and coordinate the work. That's one person's report, not a feature list, but it shows what the handoff makes possible.
The same idea appears in the SpaceXAI Team Bots launch post. It describes an engineering Team Bot that "runs Cursor cloud agents that return green, verified PRs."
Also new: team bots, finance tools, and smarter voice calls
The same week, Matt Palmer posted a "What's new in Grok Bot" walkthrough video. It covers three more updates:
- Team bots: Bots you share with your team members. Team Bots are in public beta on Teams and Enterprise plans, and the Team Bots docs explain how they work.
- Finances: searching and managing your finances with Plaid.
- Voice calls: your Bot can search your chats during a voice call and handles interruptions gracefully.
Voice chat itself is in the Chat and collaboration guide. We didn't find docs for the Plaid finance tools or for searching chats during a call, so those details come from the walkthrough.
Update, October 11: Cloud Agents, Projects and Stop
Since this post first ran, the changelog and Grok Bot's team have filled in how the handoff works day to day.
What shipped when
- September 11: when a Bot needs a repo, a card lets you connect GitHub, GitLab, Bitbucket or Azure DevOps.
- September 17: a bigger GitHub toolkit, including one pull request review covering several files. Stopping a Bot also stops the Bots and Cloud Agents it handed work to.
- September 18: a Bot can start a Project.
- September 30: the Grok Bot account announces Cursor handoff and PR management.
- October 5: PR links show a preview card on hover (v0.68.0).
The three ways a Bot can do coding work
| The Bot itself | Cloud Agent | Project | |
|---|---|---|---|
| Best for | Small edits and questions | One focused coding task | A big job with many parts |
| Where it runs | The Bot's own cloud computer, shared by all your Bots | A separate computer, under your Cloud Agent controls | Plans the work and runs its own agents |
| What you get back | An answer or a file | Usually a pull request | Results from its own agents |
| When you say Stop | The Bot stops | Stopped along with the Bot | Stopped along with the Bot |
The September 18 changelog says: "A Bot can start a Project when you ask for one: a Cloud Agent that plans the work and runs its own agents."
From issue to pull request
1. Connect your repo host. If the Bot needs access, it shows a card. Approve it and the Bot carries on. 2. Ask for the handoff in plain words. For example: "Spin up a Cloud Agent to fix issue #123 in our web repo. Add a test that fails before the fix. Open a pull request and send me the link." 3. Let it delegate. Auto-review covers delegation, so depending on your rules you may see an approval card before the Cloud Agent launches. 4. Let the Bot watch it. Lauren Tan says you can "just ask your bot to watch over your cloud agent." 5. Review the PR. PR links in chat show the number, title and status, and hovering one shows a preview card. 6. Choose where links open. A Cloud Agent's open button offers Open in Web or Open in Cursor and remembers your choice. 7. Change your mind? Say Stop. The Bot also stops the Cloud Agents it started.
For a bigger job, ask for a Project instead: "Start a Project to migrate our settings page to the new design system. Plan it, split the work, and report progress here." Tan has said you can "just ask it to spawn a project or cloud agent on any supported model":
A loop worth copying
Tan described pairing this with X monitoring on October 7: have the Bot watch X for feedback on your product, send feature requests to your issue tracker, and send bug reports to a Cursor Cloud Agent or Project to triage and fix.
Tips
- Ask for a draft PR first if you want to look before anyone else is notified.
- One task per agent. Smaller tasks give smaller diffs that are easier to review.
- Keep approvals on for merges. Connecting a repo never merges or publishes anything by itself.



