Engineering
Hit the limit? Clone a short bot from a handover.md
Long chat history burns tokens every turn — even for a tiny reply.
What hurt
Leon Poggioli (@NetSeg_io) hit usage limits spinning up bots. His article: treat long bots as disposable. Have the bot write a tight handover.md (state, decisions, open tasks, key files), clone, paste the handover as the first message, delete the old bot. Also: maintain a short state.md, kill overlapping digests, and prefer event triggers over fast polls. Not affiliated with xAI.
What to install or create
One working bot + a handover file. Clone when history gets fat. Do not invent extra spend tips — follow his article.
Bots
Working desk
Does the job. Writes handover.md when asked. Never buys usage.
Plugins
None on day one. Follow the first-run steps.
Files
handover.md. Tight state, decisions, open tasks, key files for the next bot.
state.md. Optional short living state the bot keeps current.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/NetSeg_io/status/2109805907165258016 (credit @NetSeg_io).
- 2Ask the long bot for a tight handover.md (state, decisions, open tasks, key files).
- 3Clone the bot. Paste the handover as the first message in the new one.
- 4Delete or archive the fat bot once the clone is working.
- 5Optional: add a short state.md it keeps current; prefer event triggers over 5-minute polls.
Approval fence
Do not buy extra usage without your yes. Cloning/deleting bots only.
What to tweak
Steal the handover → clone → delete path. Short current bots cost less than long ones doing the same job.
Source
Leon Poggioli @NetSeg_io · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.