Cursor: how to compact context with /summarize in Agent chat

To compact context in Cursor, type /summarize in the Agent chat input. Cursor condenses the conversation so far into a summary and frees space in the context window, without starting a new chat. In the editor /compact does the same thing, and in the Cursor command-line agent /compress is an alias. This guide is for people whose long Agent chats start to drift, slow down or hit the limit.

Everything below comes from Cursor's slash commands reference, its CLI usage guide, its 1.6 changelog and its IDE release notes. We did not run Cursor ourselves. For how usage is counted, see our guide on checking token usage in Cursor.

How to compact context in the Cursor editor

1. Open the Agent chat that has gotten long.
2. In the chat input, type /summarize (or /compact).
3. Send it. Cursor replaces the earlier back-and-forth with a summary and keeps working in the same chat.
4. If the agent is still mid-task, the release notes say you get a notice. Let the turn finish and run the command again.

Cursor's release notes for version 3.19 say /summarize also works in cloud agent chats, where the summarization runs on the cloud agent.

How to compact context in the Cursor CLI

In the command-line agent, run /summarize to free up space in the context window. The docs say /compress remains an alias, so either works. The slash commands page describes it as summarizing the conversation to reduce context.

When Cursor compacts for you

You do not always have to do it by hand. The 1.6 changelog, published on September 12, 2025, says Cursor automatically summarizes long conversations when they reach the context window limit. The manual command was added for when you want room before that point, without opening a new chat.

Later release notes changed how that works:

• Version 3.24: chats that hit the context limit now compact and continue instead of failing repeatedly. Summaries no longer drop facts from early in the conversation, and the agent keeps your latest request word for word.
• Version 3.21: long turns no longer get stuck compacting context on every step.
• Version 3.23: /summarize shows an error when it fails.

If your editor is older than these versions, updating Cursor is the first fix for chats that stall at the limit.

Other ways to reset a long chat

Compacting is one option. The slash commands reference lists others, for the CLI:

The docs list no command that shows how full the context window is, so the CLI gives you no number to watch. Cursor's docs also leave out what exactly a summary keeps beyond the points in the release notes above. Treat a summary as lossy. If a detail matters, such as a file path or a decision, restate it in your next message, or add it to a rule in .cursor/rules so it loads every time.

Which to use

Use /summarize when the task is still the same and the chat is long. Start a new chat with /clear when you are switching to a different task, because old context can only get in the way. Use /fork when you want to try a second approach without losing the first.

FAQ

What is the difference between /summarize and /compact in Cursor?

The editor release notes say typing either /summarize or /compact in the chat input triggers summarization. In the CLI, /compress is the documented alias for /summarize.

Does Cursor compact context automatically?

Yes. Cursor's 1.6 changelog says it summarizes long conversations when they reach the context window limit. Release 3.24 says chats at the limit now compact and continue instead of failing.

How do I clear context in Cursor instead of compacting it?

In the CLI, /clear starts a fresh chat session, and /new, /new-chat and /newchat do the same. A fresh chat carries nothing over, so use it when the task changes.

Does summarizing lose information?

A summary is shorter than the conversation, so some detail is gone. Cursor says that since version 3.24 summaries no longer drop facts from early in the conversation and your latest request is kept word for word. Restate anything critical to be safe.