One month of SuperGrok Heavy: 414 PRs, 92 merged
One SuperGrok Heavy seat, a fleet of Cursor cloud agents, and what git says happened.
Vineet Sharma · 19 Aug to 19 Sep 2026

- Merged92
- Closed unmerged239
- Still open83
- Cursor agents694
- Grok47
- Human accounts403
414 pull requests in one month.
92 merged.
19 Aug to 19 Sep. One SuperGrok Heavy seat.
That’s what my GitHub says.
The first 48 hours, Grok wrote the code
Day one, Grok committed straight into my repos.
43 commits and 13 PRs in two days. Backend, retailer web, customer app, scanner.
Then the weekly quota was gone.
About 36 hours.
So I split it.
Grok bots: PM and review.
Cursor cloud agents: code.

The month in git
1,144 commits.
13 repos.
28 of 32 days.

675 of those commits came from Cursor agents.
7 repos that didn’t exist on 18 Aug.
A delivery-partner app, a GST slip tool, two landing pages, three side projects.
18 Sep
208 PRs opened in one day.
Retailer web 83. Customer app 63. Backend 44. Delivery partner 14. Scanner 4.
That’s not a team.
That’s a printer.

Where the 414 went
92 merged.
239 closed without merging.
83 still open.

Most of the month was deciding what not to keep.
Three weeks later
80 small PRs folded into 3 bundles.
561 review findings on the open board. 47 rated High.
4 tickets Done. 72 In Review.
Where it landed
Writing code got cheap.
Reviewing it didn’t.
One seat bought the output.
It didn’t buy the merge button.
Source: git log across all branches and PR refs (merge commits excluded) and the GitHub PR list, 19 Aug to 19 Sep 2026 IST, pulled 9 Oct 2026. Grok’s planning-and-review role after the first 48 hours comes from my lab log, not from git. Lines of code are left out on purpose: lockfiles, build exports and bundle PRs inflate them.