In Cursor, when do you use read-only Ask mode, and when inline edit's quick question (Opt/Alt+Return), to understand unfamiliar code?
answer
- one selection versus the codebase
- Opt/Alt+Return inside Cmd/Ctrl+K
- "do it" turns an answer into an edit
- Shift+Tab or the mode picker
- switching modes starts a fresh context
basics
~20 sCursor's quick question (Cmd/Ctrl+K, then Opt/Alt+Return) asks about the selected code and can apply its suggestion when you type "do it". Ask mode, chosen in the Agent panel with Shift+Tab, explores the whole codebase read-only and never edits.
solid answer
~40 sBoth are read surfaces, scoped differently. The **quick question** lives inside inline edit: select code, press `Cmd+K` (`Ctrl+K`), switch with `Opt+Return` (`Alt+Return` on Windows/Linux) and ask about that selection; if the answer suggests a change, typing "do it" and pressing Return applies it. **Ask mode** is a mode of the Agent panel (`Cmd+I`/`Ctrl+I`), reached with `Shift+Tab` or the mode picker: Agent answers and explores the codebase without making any edits, which suits "how does the auth flow work?" or "where is the database connection configured?". For a newcomer, Ask mode maps the module first; quick questions then clarify single functions. When the questions turn into changes, Cursor says to switch back to Agent mode — and each mode keeps its own context, so switching starts a fresh context window.
go deeper
Recall that Ask mode is read-only and reached with Shift+Tab or the mode picker, and that the quick question is Opt/Alt+Return inside a Cmd/Ctrl+K prompt.
Explain the scope difference, selection versus codebase, and the "do it" step that turns a quick question into an edit. Mention that switching modes starts a fresh context window.
Describe how you would onboard into an unfamiliar module with Ask mode, quick questions and then Agent, and how you carry findings across the mode switch.
Weigh read-only exploration as a team habit: it keeps first contact with unfamiliar code free of stray edits, at the cost of a context reset when work starts.
## Two read surfaces with different scopes A developer new to a module needs answers before changing anything, and Cursor offers two places to ask. The **quick question** is a variant of inline edit: it is anchored to the code you selected in the editor. **Ask mode** is one of the Agent panel's modes — Cursor's help calls it "a read-only mode for understanding your codebase", in which "Agent answers questions and explores code without making any edits." | | Quick question | Ask mode | |---|---|---| | How to reach it | Select code, `Cmd/Ctrl+K`, then `Opt+Return` (Mac) / `Alt+Return` | Agent panel (`Cmd/Ctrl+I`), then `Shift+Tab` or the mode picker | | Scope | The selection | The codebase, explored by Agent | | Can it change code? | Yes, if you type "do it" | No, it is read-only | | Typical question | "What does this regex accept?" | "Explain the relationship between these two modules" | | Where the answer lives | The inline prompt on the selection | An Agent panel conversation | ## The quick question, step by step Cursor's inline edit help page documents it as a switch inside the same prompt: 1. Select the code you want to ask about. 2. Press `Cmd+K` on Mac or `Ctrl+K` on Windows/Linux. 3. Switch to question mode with `Opt+Return` on Mac or `Alt+Return` on Windows/Linux. 4. Type the question. 5. If the answer suggests a change you want, type "do it" and press Return. Step 5 is the feature people miss: the quick question is not strictly read-only. It answers about the selection without editing, but it can become an edit on your word. That makes it a good fit for "is this null check redundant?" followed, if the answer is yes, by "do it". ## Ask mode, step by step 1. Open the Agent panel with `Cmd+I` (Mac) or `Ctrl+I` (Windows/Linux). 2. Press `Shift+Tab` to cycle modes until Ask is selected, or choose it from the mode picker dropdown. 3. Type the question and press Return. In Ask mode Agent still searches and reads code to answer — that is what makes it useful for architecture questions — but it makes no edits. Cursor's mode table lists Ask as the one mode that cannot edit files; Agent, Plan (after you approve the plan) and Debug can. The Cursor CLI exposes the same mode with `/ask` or `--mode=ask`. ## The newcomer scenario A developer who must understand an unfamiliar module before changing it gets the most from using both, in order: - **Ask mode first**, for the map: what the module is for, who calls it, where its configuration lives. Read-only means exploring cannot leave stray edits in a module you do not yet understand. - **Quick questions next**, while reading individual functions in the editor: what a branch is guarding, why a value is cached. - **Agent mode last**, once you know what to change — Cursor's help says that for questions that lead to code changes, you switch back to Agent mode. ## Traps when moving between them - **Fresh context on a mode switch.** Cursor's help states that each mode uses its own context, so switching modes starts a fresh context window. Do not assume Agent remembers what the Ask conversation established; restate the findings or reference the earlier conversation. - **Rules still apply.** Project, user and team rules apply in Ask mode as in Agent, Plan and Debug, so Ask's explanations are framed by the same conventions. - **"do it" belongs to the quick question.** In Ask mode, a request to apply something gets an answer, not an edit; switch to Agent for that. - **Side chats are a different tool.** A side chat (`/side`) is a durable child conversation beside a running agent; it is not Ask mode, though by default it focuses on reading and answering. ## Choosing in one sentence The two also differ in where the answer stays: a quick question's answer sits on the selection in the editor, while an Ask conversation remains in the Agent panel's history, where a later conversation can be pointed back at it. Ask about **this code** with a quick question; ask about **the codebase** with Ask mode; change code with inline edit or Agent. The interview signal is knowing that the quick question can be turned into an edit and that Ask mode never edits.
- You learned how a module works in Cursor's Ask mode and switch to Agent to change it. What should you expect?Cursor's help says each mode uses its own context, so switching modes starts a fresh context window. Agent will not simply carry on from the Ask conversation; summarise what you found in the request, or point Agent at the earlier conversation, before asking it to edit.
- Is inline edit's quick question in Cursor read-only?Not strictly. It answers about the selection without editing, but if the answer suggests a change, typing "do it" and pressing Return applies that change to the selected code. Ask mode, by contrast, makes no edits at all.
- Typing "do it" in Cursor's Ask mode applies the suggested change.
- Ask mode is a separate panel unrelated to Cursor's Agent.
- Switching from Ask to Agent mode keeps the same context window.
- Project rules are switched off while Cursor is in Ask mode.
- The quick question can never change code, whatever you type.