Reset a Grok Bot chat without cloning the Bot

Grok Bot keeps durable Identity data — name, description, memory, routines, skills, connectors, and files on the shared computer — separate from the chat transcript. Cursor staff say that Identity survives Reset chat. There is still no product control labeled Compact, New session, or working-set meter on desktop or mobile.

Use Reset chat when a long thread is reloading too much context on every turn. Do not spawn a clone Bot only to “clear context.”

What staff documented

On the prune/compact thread, Cursor staff (deanrie) wrote:

1. Durable state already lives apart from the chat log and survives a chat reset.
2. Long conversations are automatically summarized as they approach the model’s context limit.
3. Auto-summarize is not the same as an explicit Compact or New session control.
4. Explicit Compact, same-Bot New session with archive, and a visible working-set token meter are not shipped yet (no timeline given).
5. Workaround when a thread grows too large: Reset chat. Settings and durable memory stay; the transcript itself is cleared (destructive for that chat history).
6. The full transcript is still sent to the model on every turn today, which is why heavy chats burn weekly usage fast — including on mobile.

Reset chat on the same Bot

1. Open the Bot whose thread you want to clear.
2. Locate Reset chat in the Bot / conversation controls (wording may read Reset chat).
3. Confirm the reset. Expect the working transcript to clear.
4. Verify the Bot still has its name, description, memory, routines, skills, and connectors.
5. Open the shared computer view and confirm durable files and logins you still need are present.
6. Send a short smoke prompt so the Bot answers from the fresh thread.

If you only need to stop runaway work, send a direct Stop now message first (Bot troubleshooting). Reset chat is for clearing the transcript, not for an emergency halt alone.

Keep Identity thin without cloning

1. Put standing instructions in the Bot description and durable memory, not in an endless chat scroll.
2. Prefer shared files on the computer for long reference material.
3. Pause or delete routines that re-send a fat conversation on a schedule. Staff elsewhere noted each routine run re-sends context.
4. Start a new Bot only when you need a different role or security-adjacent separation of conversation — not as a substitute Compact. All Bots on the account still share one cloud computer (Bot FAQ).

Pitfalls

• Reset chat clears the transcript. Export or copy anything you must keep before you confirm.
• Auto-summarize near the context limit does not give you a Compact button or a working-set meter.
• Deleting the Bot removes its profile, conversation, and routines. Hide the Bot if you may need the work later (Bot FAQ).
• Weekly burn from bot-to-bot loops and On-Demand spill are separate topics: Control Grok Bot On-Demand after weekly usage hits 100% and Understand Grok Bot usage and “Bot failed to respond”.