On July 10, 2026, Cursor shipped version 3.11 of its AI coding IDE, a workflow update built around a single idea: let a developer run more than one agent conversation at once without losing the thread. Its headline feature is Side Chats.

Side Chats

A side chat spins off from the main conversation with /side, /btw, or a plus button, and it inherits the main chat's context. Each one is, in Cursor's words, "a durable, full agent conversation that you can follow up on, revisit later, and at-mention to pull context back into the main thread." The intent is to let you "ask questions, explore ideas, and investigate tangents without interrupting your main agent conversation."

The guardrail

Crucially, side chats default to reading, searching and answering — they don't edit code unless you widen their scope. That keeps a research detour from half-committing a change or derailing your main branch of work, and it lets the primary agent keep running while you think alongside it.

Searchable history

Cursor 3.11 also makes past agent work findable. A new search returns results "that go beyond names and PR numbers," spanning transcript bodies and backed by a local index that scales to thousands of conversations. An in-conversation Cmd+F adds match counts and jump-to-match. Rounding out the release: simplified project and repo pickers that connect GitHub, GitLab and Azure DevOps without leaving the picker, and new cloud-agent hooks to observe and control agent behavior across prompts, responses, thinking, subagents and turn completion.

The bigger bet

Notably, 3.11 ships no new model and no new pricing tier — Cursor, made by Anysphere (founded 2022), is competing on IDE ergonomics rather than raw model power. The company's trajectory has been steep, from about $100 million in annualized revenue in January 2025 to $500 million by mid-year and past $1 billion by November 2025, when it last raised at a roughly $29 billion valuation. Against CLI-style rivals like Claude Code and GitHub Copilot, Side Chats stake Cursor's claim to the orchestration layer above the model.