Frontend race conditions hide from you. Cursor's debug mode came up with several theories, built a harness to test each one, cleaned up after itself and handed back a fix.
Result Cleaned up its own debugging code
“I also noticed their debug mode will now come up with several thesises (thesi?), create some sort of debugging harness and logging system, test each thesis, tear down the debugging logic and present a solution.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
Used Cursor’s debug mode on a tricky frontend race condition. It came up with several hypotheses, built a debugging harness and logging, tested each hypothesis, then removed the debugging code and presented a solution.
It helped solve the race condition. The developer also rates Cursor’s plan mode about on par with Claude Code.
There is an intermittent bug in [component]: [describe the symptom]. Don't guess a fix. List at least three hypotheses for the cause, add temporary logging to test each one, run the reproduction, and tell me which hypothesis the evidence supports. Then remove all the temporary logging and propose the smallest fix.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.