CursorContext managementLevel 3: Workflows

How Do You Ask a Quick Question Without Derailing Cursor's Agent?

Type /side or /btw in the chat input, optionally followed by your question. A side chat opens beside the main thread, knowing the parent's history. It focuses on reading and answering by default, so the main agent keeps working, and its back-and-forth doesn't enter the main conversation unless you ask.

Prompt to copy
/side Without changing any files, explain [question: why you chose this approach / what this error means / what happens if we skip this step]. Point to the files and lines you're relying on, and say if you're unsure.

Then, in the main thread:
@[side chat] Use what we found about [topic] and continue with the task.
  • Main threadthe tangent stays in context for the session
  • Side chata question, with /side or /btw
  • Forka different approach, copies the messages
Three places a question can go, based on Cursor's side chat help page.

Try it now

  1. 1While Agent is working on a task, type /side followed by a question about what it's doing.
  2. 2Read the reply in the side chat. Check that the main agent hasn't stopped and that your question isn't in the main transcript.
  3. 3If the answer matters, @-mention the side chat in the main thread. It worked if the agent acts on it. Click X to archive the side chat when you're done.

Use it when

Questions like "why did you choose this library?" or "what does this error mean?" during a long run. It's also handy for investigating a piece of a diff. Select text or a diff in the chat and choose Ask in Side Chat, or press Shift+Cmd+S (Shift+Ctrl+S).

Skip it when

When you want to try a different direction with a real copy of the conversation. That's a fork, not a side chat. Also, side chats are local-only for now, so they aren't available for Cloud Agents. And they can't be nested: start any further ones from the parent.

Why it works

Every tangent you ask in the main thread stays in its context and takes up room for the rest of the session. A side chat keeps its own transcript instead. The parent's history is copied in as hidden reference, so it knows what you're working on, but it isn't shown in the side transcript. When you want the findings back, @-mention the side chat in the main thread, and Cursor pulls in its context.

Example

Say Agent is partway through a migration, and you spot a retry library you don't recognize. Asking in the main thread would add a detour, so you type /btw why are you using this retry library rather than our existing helper? The side chat explains that it missed lib/retry.ts. You @-mention the side chat in the main thread, and the agent switches to your helper.

Going further

Forking and side chats are easy to confuse. Forking copies the conversation into a new chat: forking from the tab menu, sidebar or command palette copies every message and subagent, while forking from a message copies up to that point and drops the rest. A side chat only gives the model the parent's history as hidden context, and it's a parallel thread. Use a fork for a different approach and a side chat for a question. Note that closing a side chat archives it rather than deleting it.

Common mistakes

  • Asking every small question in the main thread, then wondering why the context is full by afternoon.
  • Expecting the parent's messages to appear in the side transcript. They're hidden on purpose.
  • Assuming the main agent sees the answer. You have to @-mention the side chat to bring it back.
  • Looking for side chats in a Cloud Agent run, where they aren't available yet.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course