Describe the request We are rewriting the app around this. We need you to ship the primitives so a Bot is an object, not an unbounded thread. Problem Each Bot is one unbounded thread. Every turn reloads the full transcript (user messages, agent messages, tool dumps, screenshots, agent-to-agent ping…

Hi Rick, thanks for the feature request. I’m combining it here in the larger thread so we can keep track of the discussion in one place!

Until something like this ships, one way to make clone-and-replace less painful: give each bot a durable notes file it owns (role, routines, current commitments, decisions and why) and have a routine rewrite it at the end of each working session. A reset or clone then just points the fresh chat at t…

Hey, thanks for such a practical approach, @Madhur_Mittal . The pattern of having one durable notes file per bot that the routine rewrites at the end of a session is a good interim solution. It works specifically because the bot’s durable state profile, memory, routines, skills, connectors, files on …

not sure I would want a button , although maybe a short term solution, long term this should be self optimizing IMO. Users should not have to make the choice, the harness should decide based on its own observations overtime. Some things in memory are more important to retain overtime. an error lo…

Thanks for the follow-up I agree it’s a separate facet — but it points at the same architectural gap. If you don’t measure the metric, you can’t optimize the platform. Without per-bot session logs (who worked, model used, tokens, cache, cost vs the weekly pool), resetting bots and clearing context …

Hey, @znuttyone . I agree, this is a separate facet, but it really comes back to the same architectural issue. Without per-bot metrics like who worked, which model, tokens, cache, and cost vs the weekly pool, any reset or clear turns into guesswork, especially when there’s not just one bot but a doze…

@deanrie , follow-up on your post #33 (Sep 23), where you wrote: “when you use a new group chat with the same Bot, the old 1:1 transcript isn’t pulled into the working set … So a new chat really starts with clean context” Based on that, I kept rotating my coordinator Bot’s work into new group roo…

Hey everyone! :waving_hand: I came across this discussion because I was facing a similar problem with my own Grok Bots. When you’re running multiple long-lived bots, context keeps growing, token usage becomes expensive, and starting a fresh conversation means potentially losing important instructi…

@eli1 , thanks for the detailed follow-up with numbers. On questions 1 and 2, the bot’s self-report about its own context isn’t a very reliable signal. The model can describe things that aren’t actually in its working set. Also, the bot’s durable memory is shared across all of its chats, so it may “…

@deanrie thanks. Grok Bot 0.71.2, stable, Windows 11 Pro. I checked the visible messages of both rooms and found no literal old-room quote in the new room. I couldn’t check tool outputs. Three yes/no questions: Is there a supported way to view a bot’s own memory and delete old items? I see two (…

Grok Bot: prune/compact an agent’s context without creating a new Bot

Ideas Feature Requests

DannyB (Danny) October 19, 2026, 7:54pm 47

@eli1 For question 2 see:

Topic		Replies	Views
Grok Bot / agents: context compaction, clone-replace for hung chats, and per-bot usage telemetry Feature Requests context , grok-bot	0	66	September 29, 2026
Grok Bot context window size and token accumulation logic in Pro+ Help context , grok-bot	8	666	September 22, 2026
Shared Grok Bot team across teammates (same roster, separate chats) Feature Requests teams-enterprise , grok-bot	11	939	September 30, 2026
Duplicate Bot - Missing? Help context , docs , grok-bot	2	105	September 26, 2026
"Squeeze" button - compact the current chat in place instead of starting a new session Feature Requests chat , context	1	104	August 27, 2026

Grok Bot: prune/compact an agent’s context without creating a new Bot

Related topics