Cursor 3.11 Lets Developers Run Parallel AI Chats Without Stopping Their Agent

Cursor just shipped version 3.11, and the headline feature is deceptively simple: you can now open a side chat while your main agent is still running. But zoom out and this update is really about one thing -- making it less painful to manage the growing complexity of long-running, multi-agent workflows.

The problem with one conversation at a time

As Cursor has evolved into a full agent platform, a tension has emerged. The working life of a software engineer has become increasingly complex -- a single engineer might oversee dozens of coding agents at once, launching and guiding different processes as necessary. It's a lot to keep track of, and human engineers' attention has quickly become the limiting resource. The old single-thread chat model just doesn't fit that reality.

Before this release, asking a clarifying question mid-task meant either interrupting the agent or holding the thought in your head until it finished. Neither is great when you're deep in a refactor.

Side chats: parallel thinking without the context switch

You can open a side chat to ask questions, explore ideas, and investigate tangents without interrupting your main agent conversation. Use /side, /btw, or the plus button at the top of the chat panel to create a new side chat that has context from the main chat.

Each side chat is a durable, full agent conversation that you can follow up on, revisit later, and at-mention to pull context back into the main thread. That last part matters -- it's not a throwaway scratchpad. You can @mention a past side chat to inject its conclusions directly into your main conversation.

By default, side chats focus on reading, searching, and answering. Use them to ask clarification questions, research alternatives without committing to a pivot, and sanity-check a decision while the main agent continues running.