BuildGist

Cursor says your conversation is too long: what to do

Kayvan Zahiri ·

When Cursor says your conversation is too long, start a new chat and bring the old one in with @Chats, plus @Commit (Diff of Working State) so the new chat sees what the agent changed. In the Cursor CLI you can try /summarize first, which shrinks the conversation so you can keep going in the same chat.

The message people see

Cursor's documentation does not print this error. On the Cursor community forum, a user quoted it in July 2025 like this:

Your conversation is too long. Please try creating a new conversation or shortening your message.

That reporter got it after short prompts, even in brand-new chats, and a reply in the thread said they were investigating and asked for the request ID. So the message can mean the chat really has outgrown the model's context window, or it can be a bug. If it shows up on the first or second message of a fresh chat, report it on the forum with the request ID.

Why a long agent chat fills up

An agent chat carries its history with it: your messages, the agent's replies, and the file reads, searches and tool results it pulled in along the way. Once it no longer fits the model's context window, the next turn has nowhere to go.

Start a new chat that knows the task

Cursor's @ mentions help, read on October 19, 2026, lists what you can attach by typing @ in the chat input:

Then say the task in your own words. Something like this, filled in:

Picking up from the chat I attached with @Chats. It got too long.
Goal: (one line)
Already done: (see the @Commit diff)
Still open: (what is left)
Don't: (what we already ruled out, and why)
First: (the next step). Say it back to me before you edit.

Resist reattaching every file the old chat touched. The point of the new chat is a short history, and the diff plus your note carry most of what matters.

In the Cursor CLI: summarize first

Cursor's CLI slash-command list, read the same night, includes /summarize, which summarizes the conversation to reduce context. /compress is an alias. Also on that list:

The docs list /summarize for the CLI only. They do not document a summarize command in the editor's agent chat, so this page does not promise one there. In the editor, start a new chat.

Keep tangents out of the main chat

Many chats get long because of side questions. Type /side or /btw to open a side chat. Cursor's side-chat help says it is a durable conversation with its own transcript. It uses the parent thread as hidden reference context, and its follow-ups do not appear in the parent transcript. When you have the answer, @-mention the side chat in the main thread to pull that context back. Side chats are local only for now, not in Cloud Agents.

Forking from a specific message is another way back. Cursor's side-chat help says it copies the conversation through that message and drops everything after it.

Max Mode, if your plan has it

Max Mode extends a model's context window beyond the default. Cursor's models-and-pricing page says it is available only on legacy request-based plans, billed at the model's API rate plus 20%. On those plans you turn it on in the model selector, and a larger window can mean more tokens per request. On any other plan there is no Max Mode to switch on, and a new chat is the fix.

Which of these is your situation

Or move the task to Claude Code or Codex

A full chat is a natural point to switch agents. Before you do, look at what the long chat actually changed. Agent Review and the Agents Window diffs view are in how to review Cursor agent changes. Claude Code or Codex opened on the same project folder reads the files Cursor changed, committed or not. What it lacks is the task, and the note above covers that.

BuildGist can carry the task instead. When you start a new chat in Claude Code or Codex in the same project, a BuildGist card offers Cursor's task. Choose Continue and the chat starts with that context, or Start fresh to skip it. If Codex is the one that filled up, see Codex ran out of room in the context window. Moving work among all three agents is in how to keep context across Claude Code, Cursor and Codex.

Sources

What you need

Codex needs you to approve BuildGist once, in Codex. BuildGist shows the steps. Setup is in Getting started.

To explain a run, your computer sends BuildGist what that run needs, and BuildGist passes it to Anthropic. BuildGist does not keep this material. It does not send your whole repository, files the run did not change, or files named like secrets, such as .env files and keys. It keeps the explanation and short cited excerpts of changed code, at most 12 lines each. Secret masking is best-effort. Privacy has the full list.

Every account gets 7 days of BuildGist Pro free, with no card. The 7 days start at your first explanation or Continue handoff. Nobody is charged when the trial ends. After that, BuildGist Pro is $12 per month, plus any applicable tax shown at checkout. See pricing.

Try BuildGist Download for Mac

Apple silicon, macOS 12 or later. United States, 18 or older.

Related

Questions: kayvanandre@gmail.com.