Ask a Scoped Codebase Question
Make the first question specific enough for Cursor to answer from evidence.
Use the right surface
After this you can pick Ask, context and search for the right job and define done.
Done means you can ask Cursor a bounded question and validate the answer against files it cites.
Ask mode should leave you with cited files you can open and inspect.
Use Ask, context and search when you need to understand a flow before changing it. 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
- Ask modeA read-only mode for asking questions about a codebase without changing files; the safe way to explore unfamiliar or legacy code. with selected files, folders or natural-language search
- Source
- Cursor Learn context guide and prompting docs
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 you can ask Cursor a bounded question and validate the answer against files it cites.
Self-check
QWhen should you reach for Ask, context and search?
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.
- 1Name the flow you want to understand and the specific outcome you care about.
- 2Attach one or two likely files or let Cursor search when you are not sure where the code lives.
- 3Ask for the route through the code, not a generic explanation of the whole repo.
- 4Open the cited files and confirm the answer before treating it as your map.
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.
The answer explains the flow in order, not only a component list.
Takeaway. Stop when you have proof: The response names concrete files or symbols you can inspect..
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?