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 Grok setup of research, classifier, builder, tester, reviewer, and security bots maps repos, makes minimal changes, runs tests and lint, and opens draft PRs; the author reports over 1,000 PRs.
A Grok setup of research, classifier, builder, tester, reviewer, and security bots maps repos, makes minimal changes, runs tests and lint, and opens draft PRs; the author reports over 1,000 PRs.
The author set up six sequential Grok bots. The first reads the issue and maps the repo to relevant files and prior PRs, passing only useful context. The second classifies the task and risk level to route it. The builder writes the smallest possible code change. A tester bot then runs tests, lint, type checks and builds, feeding failures back to the builder. A separate reviewer examines the diff for regressions and missing tests. A final security bot checks secrets, auth and dependencies before opening a draft PR.
The loop produced over 1,000 PRs. No shortfalls are stated.
Set up a team of bots for my repo [repo URL]: one maps the codebase, one classifies the task from [issue tracker or label], one builds a minimal change, one runs tests and lint, one reviews, and one checks security. Each task should end in a draft pull request with a summary of what changed and the test results. Never merge or push to the main branch; leave every PR as a draft for me to review.
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.