Coordinate sub-agents to monitor PRs and fix prod bugs
A Cursor Projects coordinator agent delegates to sub-agents, watches new PRs and production bugs, spins up agents to fix issues, and surfaces questions to the user.
A guide to building agents that open, review, and merge pull requests.
A guide to building agents that open, review, and merge pull requests.
The guide breaks a software factory into five stages: intake, isolation, tools, verification and a merge gate. It draws on published setups from Stripe, Spotify, Shopify and Ramp. It gives configs for each stage, including an issue filter, git worktrees per agent, a shared MCP tool block, a screenshot-verification skill and tiered merge rules. A human reviews at the end.
Microsoft's dotnet/runtime data shows agent PRs merging 67.9% of the time against 87.1% for engineers, and 55.1% when fully autonomous. Review capacity becomes the bottleneck, and proven results are mostly mechanical migrations.
Build the gates before the fleet, and start with one gate where agents cause the most rework. Worktrees start empty, with no .env, dependencies or free port, and non-interactive runs don't clean up after themselves.
Set up a workflow for the repository [repo name] where an agent picks up issues labeled [label], opens a pull request with a fix and tests, and a second agent reviews it. Write the configuration and a short guide for how it runs. Do not enable automatic merging yet; show me the merge rules you propose and wait for my approval.
A Cursor Projects coordinator agent delegates to sub-agents, watches new PRs and production bugs, spins up agents to fix issues, and surfaces questions to the user.
Ran a Cursor agent continuously for 24 hours to build a project management tool; the app fully works but is not production ready.
The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.