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 developer used Cursor and Warp agents to analyze NestJS database queries and recommend indexes for a production performance problem.
A developer used Cursor and Warp agents to analyze NestJS database queries and recommend indexes for a production performance problem.
A page was slow in production but not in the dev environment. The developer asked a Cursor/Warp agent to list possible causes and the steps to fix them. The agent read the codebase, worked out which database queries NestJS was making, and said which database indexes should be used.
After the developer added the recommended indexes, page load performance improved significantly. The source gives no timings or figures.
The agent worked from the codebase and produced a list of candidate causes, so the developer still had to apply the indexes and check the result in production.
Our [framework, e.g. NestJS] app is slow in production but not locally, specifically [endpoint or page]. Read the code and database queries involved, identify the slowest or most repeated ones, and recommend indexes or query changes with an explanation of why. You're done when you have a ranked list of fixes with the exact migration or code change for each. Don't run anything against the production database; show me the changes first.
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.