2 min lesson
Run one Debug Mode evidence loop
Capture one failure, identify its cause from logs, apply a targeted fix and remove the instrumentation.
Step 1 of 2
Give Debug Mode the expected result, actual result and exact steps for one reproducible bug. Read its hypotheses and the files it inspected. Let it add focused logs, then repeat the steps without changing the test data. Use the captured values to identify the cause. Apply the targeted fix, repeat the same reproduction and inspect the final diff to confirm that every Debug Mode log was removed.
Debug Mode: prove it before you fix it
0:33 · narratedRead this demo as text
- Debug Mode, not a guess-and-patch Agent run. Send the bug and make it list hypotheses before it touches a file.
- See that? Probes first. Reproduction steps wait for you. No silent rewrite while you are still blind.
- Hit Proceed after the repro. Narrow fix in the file searchFilter.ts, same script again — matchesExpected true. That is the loop.
Practice next: Now do the module workflow: reproduce first, demand hypotheses before edits, and clean up instrumentation.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.