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.
Bots check PRs every 30 minutes, send failures back to a cloud agent, review clean PRs and auto-merge high-confidence, low-risk ones.
Bots check PRs every 30 minutes, send failures back to a cloud agent, review clean PRs and auto-merge high-confidence, low-risk ones.
Each engineer bot keeps a shared Notion database of PRs. Every 30 minutes it checks each PR for Bugbot or security comments, failing CI and merge conflicts. Problems go back to the cloud agent, and the row moves to Working. Clean PRs are marked Ready for Review and get a review run. Highly confident, low-blast-radius PRs are merged automatically. The author reviews the rest.
The author finds tasks ready to merge almost every morning. The fleet manages over 200 cloud agents at once, up from about 15 by hand. The source gives no merge-rate figures.
The author says rapid transcript-checking routines, like the 5-minute P0 mode, burn tokens faster than expected, so keep them for true urgency.
Every 30 minutes, check open pull requests in [repo]. Send failing PRs back to a coding agent to fix, and review the clean ones. Only auto-merge a PR if you are highly confident and it is low-risk, such as [examples]; otherwise ping me with a summary. Pause and ask me before merging anything that touches [sensitive areas].
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.