Grok Bot's Hidden Lock-In: No Memory Export, 20-Run History Ceiling, Shared Cloud Machine

If you're building persistent workflows on Grok Bot (or any AI agent platform), the exit cost might be higher than you think. A detailed post on r/openclaw breaks down xAI's official documentation, revealing hard limits that turn 'switching costs' from an abstract risk into a concrete, pay-up-or-rebuild decision.

The Hard Ceilings in xAI's Docs

According to the source, xAI's own materials state three things that fundamentally shape your relationship with the platform:

• Routines are capped at 50 per Bot, and only the 20 most recent runs are kept. Your execution history has a hard ceiling.
• Deleting a routine is permanent. No trash, no restore. Deleting a Bot nukes its routines with it.
• There is no memory export. Not 'it's awkward' — there is no path to get your data out.

Why This Is Worse Than Model Lock-In

With a model API, you own your prompts and can re-send history. Swapping GPT for Claude is a config change. Grok Bot isn't stateless — it's a stateful execution environment where value compounds inside the vendor:

• Every crawled page, run search, and API call lives on their servers.
• Six months of 'no, not like that' feedback and all the changes it triggered.
• The routine order and dependencies between your Bots.
• Every dead end already tried, so the next run avoids it.

Leave, and your new stack starts blind. It re-crawls, re-searches, re-parses — and re-derives conclusions you already paid for once. That costs time and money, and it's why the switching cost becomes the moat.

You Can't Even Tell What Model You're On

xAI hasn't disclosed which models the router selects, and there's no documented way to pin or switch. If your automations start producing worse output, you won't know if the router moved you to a cheaper model, a model got updated, or your prompts were always fragile. A price increase is visible; silent behavior drift isn't.

Not a Grok Bot Problem — a Category Problem

The post is careful to note this isn't unique to Grok Bot. Claude Cowork, ChatGPT Work, and Copilot Cowork are built the same way: give an agent your logins, let it accumulate state, and watch that state become the thing you can't leave behind.

What to Do About It

The practical takeaway: treat the agent platform as the execution engine, but keep the memory somewhere you own. Send everything to a place you can control. Before building deep, ask yourself: what happens if the bundle reprices, a regulation hits your domain, or a better open-source stack ships?