Long chat? Keep your progress. Start fresh with a clear handoff.
For people already working in Grok Bot. Save your decisions, tasks and key references in a handoff you can review before moving to a new bot. Free and open source.
Already have a long chat? Copy the prompt into that bot. Starting from scratch? Open the new-bot template. Requires access to Grok Bot.
Free & open source (MIT)
No account on this website
Unofficial community project
Your bot
How are we doing?
🟢 Green · all good. About 20 messages in. Chat away, I've barely warmed up.
🟡 Yellow · time to summarize. About 55 messages in. I've saved where we are in STATUS.md, so we can pick it up anytime.
🔴 Red · fresh bot time. About 90 messages in. Your handoff file is ready: memory, tasks and key files. A new bot can pick up right here.
Tap a light ↑
Get started
Up and running in 3 steps
Nothing to download. No coding. If you can click, you can do this.
Use your existing bot
Copy the installation prompt below into the Grok Bot where your work already lives. For a new project, use the new-bot template instead.
Save a checkpoint
Ask it to save the goal, decisions, open tasks and key references. Review what is missing before you move.
Review before moving
Use Context Bot Migrator when you are ready. Keep the old bot as a fallback and verify the new one. Explore an illustrative handoff; this demo does not migrate a real bot.
Already have a bot? Paste this prompt into its chat:
Install the skill at https://contextbot.app/skill.md into my skill library, save it exactly as written, then confirm.
The demo
A visual introduction
Illustrative overview, not a measured before-and-after benchmark. Try the sample handoff below; a real migration still needs verification.
0:001:10
Now, the long version ↓
The problem
Sound familiar?
A long chat can become harder to follow. Before starting fresh, keep a reviewable record of the work that matters.
🐢
The bill
Your weekly usage runs out faster than it should, and you can't tell why.
💸
The wait
You ask something simple. You make a coffee. It's still typing.
😬
The fear of starting over
You want a fresh conversation, but re-explaining decisions and unfinished tasks takes work.
Why it happens:long conversations can increase input usage. Actual cost and speed depend on the model, caching, tools and platform. A checkpoint alone does not clear the chat history.
Context Bot helps organize a handoff. It does not guarantee faster replies, lower usage or a lossless migration.
Without Context Bot
You notice the cost when your week's usage is already gone.
You keep stretching one endless chat because starting over feels risky.
A new bot means re-explaining your preferences, decisions and files.
Routines quietly use up your allowance in the background.
With Context Bot
An approximate color suggests when to review the chat.
You summarize at yellow and switch at red, on your terms.
A handoff file carries memory, tasks and key files to the new bot.
The dashboard flags the routines worth pausing or spacing out.
How it works
It starts with a traffic light
Your bot keeps an eye on how long the conversation is getting and shows it to you as a color.
Scroll down the road: the light changes as the chat grows.
Fresh and fast.Getting a bit slow…Running on fumes.
Message 1 ↓
Green
All good. Carry on.
Short chat · little pasted material
Chat away. In the background, your bot keeps a short STATUS.md with where things stand.
Yellow
Time to summarize.
Growing chat · review your checkpoint
Your bot saves a checkpoint in STATUS.md. Writing a summary does not remove the old history from the current conversation.
Red
Move to a fresh bot.
Heavy chat or missing details · review a handoff
Review the handoff, move to a fresh bot when authorized, and verify decisions, tasks and file access before continuing.
EXITFresh bot
Message counts are rough cues, not context percentages or token measurements. Long documents can outweigh many short messages; a color cannot guarantee available capacity.
Context Bot Migrator
Move to a fresh bot, calmly and step by step
Context Bot Migrator prepares a handoff for your review, then helps create a new bot and verify its setup after your confirmation. Keep the original as a fallback. Access to files, connectors and routines must be checked; a summary cannot guarantee that every detail carries over.
It reads the old chat
The Migrator reads the old bot's conversation itself and writes a short, structured handoff file (TRASPASO.md): memory, rules, tasks, files, skills, routines and connectors.
The old bot double-checks it
It sends the file to the old bot (required), which adds whatever is missing and lists all its routines.
You skim it and say yes
You get the full file as an attachment, with a short summary on top. Look it over in detail if you like. Nothing is created until you say yes.
New bot, routines swapped safely
It creates the new bot with routines paused and checks it against a list. The old bot pauses its routines, and the new ones switch on after your second yes.
It checks everything matches
It compares counts before and after (memory, skills, routines and schedules) and flags connectors that need signing in again. If a step fails, it tells you what to do and tries again from there.
Final message, with a way back
It sends you a final message so you pick up where you left off. The old bot stays hidden, never deleted, so you can always go back.
Opens the Migrator template in Grok Bot. Prefer the skill? Get it on GitHub.
Optional tools and tipsSavings mode
Less repetition. Reports in one place.
Savings mode can suggest scripts for mechanical tasks or a single Page for recurring reports, with scheduled updates and brief linked notifications. Every change needs your confirmation. Generating and updating reports still uses allowance; savings are not guaranteed.
Bot does everything
You ask for the same conversion again, and the bot does every step.
A routine reads the files, does the sums and writes the report, every day.
Each of those steps uses your allowance.
Script or Page + brief notification
A script on the box does the mechanical part: “run csv-convert”, or cron.
A recurring report can stay in one Page; the routine updates it and sends a brief link, including on failure.
Judgement and writing stay with the bot.
How it spots repeats without re-reading your chat
tareas.log 2026-11-04 | csv-convert | sales CSV to xlsx
scan (weekly) 4x | csv-convert | 2026-11-04 | sales CSV to xlsx
bot “You've asked for this 4 times. Want a script for it?”
It notes tasks as it goes, a script does the counting, and the bot only reads a 10-line summary during its usual size check, about once a week. Say “savings mode now” to check anytime.
📝
(a) Repeated requests
One short line per finished task in a log. The bundled script counts keys repeated 3+ times in 30 days, with no bot usage.
🔁
(b) Your routines
The bot reads only each routine's saved prompt text, not its runs, and flags the mechanical parts: fetching data, reports, backups, conversions, checks.
🛑
Nothing changes without your OK
One proposal at a time, only after confirmation. Reuse an existing reporting routine, verify the export and show the last successful update with its time zone. Never label stale data as fresh.
Try it: tell your bot “Savings mode now”
The complete kit
Three friendly bots, one complete kit
Together they keep your bots in shape and help your subscription go further. All free and open source.
🚦 Context Bot · your companion in long chats
It keeps an eye on chat size with a traffic light, saves your progress in STATUS.md and prepares the handoff so you can pick up right where you left off. Its savings mode suggests scripts for repeated tasks and routines.
🧭 Context Bot Migrator · a calm move to a new bot
It guides you step by step, copies without moving or deleting the old bot, pauses routines, verifies with a checklist and lets you roll back.
🪶 Context Bot Lite · just the traffic light
The light version: traffic light and STATUS.md only, with fewer checks.
💛 Free, open source, yours
MIT licensed, no sign-up, and nothing changes without your OK. Add the ones you need from a ready-made template.
Context Bot Lite
Just the traffic light, nothing else
For bots that only need a gentle eye on chat size. Lite keeps the traffic light and a STATUS.md, checks about every 20 messages or when you ask, and skips savings mode and migration. When it reaches red, it suggests Context Bot Migrator.
🚦 Traffic light
Green, yellow or red, with one short sentence when it changes.
📝 STATUS.md
Your progress in a file, so you can pick up where you left off.
Paste this into any Grok Bot. It answers in a few lines with its traffic-light colour and one tip, without heavy tools.
Copy this prompt
Quick check: based only on the context you can currently see, identify whether the conversation is short, growing or difficult to follow. Do not use tools or read files. Use green, yellow or red as an orientation, not a token or capacity measurement. If you cannot assess it, say so. Reply with the color, the visible reason and one next step: continue, save a checkpoint, or review a handoff. Do not invent percentages or promise savings.
It is an estimate: bots cannot read their exact context size.
Bonus
Tips to make your week last longer
Small habits that make your weekly usage go further. Each one links to its source.
Yes. Free and open source under the MIT license. No paid tier, no catch.
Do I need to know how to code?
No. Click Add Context Bot, add the template and chat as usual. Already have a bot? Paste one prompt into its chat instead.
Template or prompt: which one?
The template creates a new bot with the Context Bot skill and its instructions ready to go. The prompt adds the same skill to a bot you already have, so it keeps its chat, memory and setup. The light works the same either way.
Why does my new bot have a black ball as its picture?
Templates don't carry the profile picture, so the bot starts with the default one. Download its picture and set it yourself: Context Bot, Migrator, Lite.
Will I lose my work when I switch bots?
A new bot doesn't inherit the old one's learned memory, so before you switch, your bot writes a handoff file with your preferences, decisions, tasks and key files. The new bot reads it and carries on. Check the file first: it should never contain passwords or keys.
Do I have to copy and paste anything to migrate?
The Migrator is designed to read the old chat and coordinate the handoff through available tools. If it cannot access a bot or connector, it must explain the limitation. Review the handoff and confirm creation and routine activation separately.
Does it read or upload my conversations?
The skill works inside your Grok Bot, and the Migrator reads the old chat when you authorize a migration. The website does not receive that conversation. The local dashboard stores data in your browser; connecting optional live status sends bot names, colors and estimates to the connector.
How accurate is the light?
It is a qualitative cue based on visible chat content. It cannot measure remaining capacity or convert a message count into a reliable percentage. Review the checkpoint when important details are missing.
Is it an official Grok Bot product?
No. It's an unofficial community project, not affiliated with Grok Bot or xAI.
Keep a checkpoint before you start fresh.
Use your existing bot or start a new one. Check the handoff before switching.
