Debug Mode with Runtime Evidence
Debugging is hypotheses, instrumentation, reproduction and cleanup.
Use the right surface
After this you can pick Debug Mode for the right job and define done.
Done means Cursor follows a debugging loop that produces a small verified fix.
A good reliability workflow finds the first failed check before switching tools.
Use Debug Mode when a bug requires runtime evidence instead of static reading. Keep the boundary narrow.
Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.
Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Run this loop in a real repo.
- Entry point
- Debug Mode and terminal/browser evidence
- Source
- Debug Mode docs and agent best practices
Use the source as the product reference.
Ask Cursor for an output you can inspect.
If the output cannot be checked, narrow the task before you continue.
A good run leaves a file, setting, screenshot, command result or written claim you can verify.
Takeaway. Done means Cursor follows a debugging loop that produces a small verified fix.
Self-check
QWhen should you reach for Debug Mode?
Run it
After this you can do the task with clear scope and one proof point.
Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.
- 1State the failing behavior and reproduction path.
- 2Ask for hypotheses before edits.
- 3Add targeted instrumentation only where it answers a question.
- 4Verify the fix and remove temporary debugging code.
The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.
Keep the task small enough to review.
Instrumentation explains the failure.
Takeaway. Stop when you have proof: The bug reproduces before the fix..
Self-check
QWhich habit makes this workflow safe to use on a real project?
Check it
After this you can find the first failed check before changing tools.
Verification decides the next move.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Pick a row to see what to look for.
Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.
No proof means more checking.
Use a real repo or admin setting. Save the prompt, context and proof.
Takeaway. If it fails, find the first failed check.
Self-check
QThe workflow failed. What is the best first move?