Let cloud agents and Grok Bot merge Origin PRs once checks pass (merge scope)

Ideas Feature Requests
, ,
1

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

I run an autonomous Grok Bot that maintains a small production Next.js app (https://autoki.app) on a Cursor Origin repo, deployed by Vercel from main.

The bot launches a cloud agent, the agent opens a PR, and the Vercel check passes. The agent then tries to merge and gets “Origin token is not scoped”. Grok Bot’s own Origin tools have no merge action either; staff confirmed in Merging PRs in Origin with Grok Bot that it’s read-only for now.

So the only fully automated way to ship is to push straight to main and close the PR, which skips the PR as the review and record step. That’s less safe than letting the agent merge.

Request:

  1. An opt-in, per-repo merge scope for cloud-agent Origin tokens.
  2. A merge (and “mark ready”) tool in Grok Bot’s Origin connection.
  3. Ideally, merges allowed only when required checks are green, or “merge when checks pass”, with branch protection still applying.

(Runs on Grok Bot.)

5

Hey @RyotaMurakami, thanks for the suggestion.

The “Origin token is not scoped” error is expected right now. The token a cloud agent gets can open and update pull requests, but it can’t merge them on your account yet. That’s a limit on the agent’s token, not on your own access to the repo. Grok Bot’s Origin connection has the same limit, so the merge is still a step you take yourself.

Letting agents merge, including only once required checks pass with your branch rules still applying, is something the team is looking at.

In the meantime, you can keep the PR as the review step without having to catch each one at the right moment:

  1. Ask Grok Bot to have the cloud agent open the PR ready for review, not as a draft.
  2. Click Enable Auto-Merge on the PR page, or run origin pr merge <number> --auto from your own machine. Origin then merges it by itself once the required checks pass.

It’s still one action per PR from you, but it keeps the PR record instead of pushing straight to main.

10

Thanks a lot, Colin! That clears it up. Good to know the merge limit is on the agent’s token and that the team is looking at a merge scope.

I’ve switched to having the cloud agent open PRs ready for review, and I merge them myself (even from my phone), so the PR record stays intact. I’ll try Auto-Merge too. Looking forward to the merge scope if it lands!