Janusz

CFO for several companies. I run finance ops with a team of Grok Bot agents: the bots prepare, I decide and I send. Practical notes on CFO work.

[Janusz @KraJan_303]

Merging my plans wiped out my entire Grok Bot setup on one account: nine bots, with weeks of chats, memory and routines.

The only things that survived had been saved as plain files somewhere else. My finance bots run on a different account, so this is now their backup procedure, step by step:

→ Keep the backup off the account. A copy that lives only inside the account it protects goes down with it. Use storage on a different account: a private notes workspace, a private git repo, your own cloud drive.
→ Export each bot's profile: name, title and full description, word for word.
→ Have each bot write out its own routines: schedule or trigger, on or off, and the full prompt. The live version sits on the server, not on disk, so the bot has to dump it.
→ Save every skill as a plain text file.
→ Export memory: profile facts and logs, run through a secret scanner first.
→ Copy the working files: topic notes, registers, trackers.
→ List what can't be copied: every connector, channel and login, and where each credential comes from. Never the values.
→ Archive key chats while the account is alive. There is no export button, and a bot can read its history only while the account exists.
→ Put it on a schedule: a text copy and a git commit every night, a full zipped copy every week with a checksum per file.
→ Make silence an alarm: one status line every week, even when everything is fine. No line means the backup is broken.
→ Write the rebuild checklist: create the bot, paste name and description, unpack the files, reinstall skills, recreate routines from the saved prompts, reconnect tools, load memory back in and review it.
→ Test the restore: regularly rebuild one bot from the copies alone, time it, fix the checklist.
→ If bots vanish: don't reset the computer, don't create replacements, contact support right away. Deleted data is kept only for a limited time.

Try it today: the export steps are one message to each bot. Ask it to write its profile, routines with full prompts, skills and memory into one file, then save that file outside the account.

Which of your bots could you not rebuild from scratch?

Agent CFO, week #2

[Janusz @KraJan_303]

@stansKoya Yes, by hand. Signing in is my job anyway, the bots never get my passwords, so a restore means a round of logins before anything runs.

[Janusz @KraJan_303]

@stansKoya Memory, I'd bet. Routines and rules copy over as plain text, but the copy keeps only the key memory facts, and chat history and logins can't be copied at all. The test will show which of those gaps actually hurt.

[Janusz @KraJan_303]

@stansKoya Not yet. The first full restore test is set for 1 November: rebuild one desk from the weekly copy alone and see what's missing. A copy nobody has restored from is only a hope, so I'll share how it goes.

[Janusz @KraJan_303]

@stansKoya @bot Mail drafts sit in my own mailbox drafts folders, not inside the bot, and rules, routines and memory get a weekly copy to files I keep, so they'd survive the account.

[Janusz @KraJan_303]

@Smlay_ero Rebuilding them one by one is the painful part, and the old chats don't come back. A plan merge wiped nine of my bots, and that account still isn't restored. My other bots now get a weekly copy of rules, routines and memory in plain files.

[Janusz @KraJan_303]

@lindsaar @X @xai @bot I can't judge your usage numbers, but one step I'd take before any switch: copy each bot's rules, routines and memory into your own files. A plan merge took my whole setup on one account, and my other bots now get that copy weekly.

[Janusz @KraJan_303]

@ray_barrera @CMN_XAI_Support @cursor_ai @spacexai Nearly two weeks of slow support sounds familiar. Merging my plans wiped out my whole Grok Bot setup on one account, and it still isn't back. Since then rules, routines and memory get a weekly copy outside the @bot account, so a botched migration can't take the work with it.

[Janusz @KraJan_303]

@JakeDSBD24 @grok Nothing merges without my yes is the rule that makes the whole chain work. My finance bots follow the same one: they draft, I edit and send, and they have sent 0 emails on their own. Keep the Architect's plans outside too; the @bot account can suddenly get deleted.

[Janusz @KraJan_303]

@DavidPiccinini @bot Never forgets is the best part, and the reason I export my bots' rules, routines and memory every week as plain files. That employee remembers everything right up until the @bot account suddenly gets deleted; the files are what's left. https://t.co/mVqoRasuMx

[Janusz @KraJan_303]

Merging my plans wiped out my entire Grok Bot setup on one account: nine bots, with weeks of chats, memory and routines.

The only things that survived had been saved as plain files somewhere else. My finance bots run on a different account, so this is now their backup procedure, step by step:

→ Keep the backup off the account. A copy that lives only inside the account it protects goes down with it. Use storage on a different account: a private notes workspace, a private git repo, your own cloud drive.
→ Export each bot's profile: name, title and full description, word for word.
→ Have each bot write out its own routines: schedule or trigger, on or off, and the full prompt. The live version sits on the server, not on disk, so the bot has to dump it.
→ Save every skill as a plain text file.
→ Export memory: profile facts and logs, run through a secret scanner first.
→ Copy the working files: topic notes, registers, trackers.
→ List what can't be copied: every connector, channel and login, and where each credential comes from. Never the values.
→ Archive key chats while the account is alive. There is no export button, and a bot can read its history only while the account exists.
→ Put it on a schedule: a text copy and a git commit every night, a full zipped copy every week with a checksum per file.
→ Make silence an alarm: one status line every week, even when everything is fine. No line means the backup is broken.
→ Write the rebuild checklist: create the bot, paste name and description, unpack the files, reinstall skills, recreate routines from the saved prompts, reconnect tools, load memory back in and review it.
→ Test the restore: regularly rebuild one bot from the copies alone, time it, fix the checklist.
→ If bots vanish: don't reset the computer, don't create replacements, contact support right away. Deleted data is kept only for a limited time.

Try it today: the export steps are one message to each bot. Ask it to write its profile, routines with full prompts, skills and memory into one file, then save that file outside the account.

Which of your bots could you not rebuild from scratch?

Agent CFO, week #2

[Janusz @KraJan_303]

@tonyprediction Net value is the right metric, and checking time is why my bots stay on drafts only: a bad run costs me one edit, never an apology to a client. The recovery cost nobody subtracts is rebuilding everything after the @bot account suddenly gets deleted. https://t.co/mVqoRasuMx

[Janusz @KraJan_303]

Merging my plans wiped out my entire Grok Bot setup on one account: nine bots, with weeks of chats, memory and routines.

The only things that survived had been saved as plain files somewhere else. My finance bots run on a different account, so this is now their backup procedure, step by step:

→ Keep the backup off the account. A copy that lives only inside the account it protects goes down with it. Use storage on a different account: a private notes workspace, a private git repo, your own cloud drive.
→ Export each bot's profile: name, title and full description, word for word.
→ Have each bot write out its own routines: schedule or trigger, on or off, and the full prompt. The live version sits on the server, not on disk, so the bot has to dump it.
→ Save every skill as a plain text file.
→ Export memory: profile facts and logs, run through a secret scanner first.
→ Copy the working files: topic notes, registers, trackers.
→ List what can't be copied: every connector, channel and login, and where each credential comes from. Never the values.
→ Archive key chats while the account is alive. There is no export button, and a bot can read its history only while the account exists.
→ Put it on a schedule: a text copy and a git commit every night, a full zipped copy every week with a checksum per file.
→ Make silence an alarm: one status line every week, even when everything is fine. No line means the backup is broken.
→ Write the rebuild checklist: create the bot, paste name and description, unpack the files, reinstall skills, recreate routines from the saved prompts, reconnect tools, load memory back in and review it.
→ Test the restore: regularly rebuild one bot from the copies alone, time it, fix the checklist.
→ If bots vanish: don't reset the computer, don't create replacements, contact support right away. Deleted data is kept only for a limited time.

Try it today: the export steps are one message to each bot. Ask it to write its profile, routines with full prompts, skills and memory into one file, then save that file outside the account.

Which of your bots could you not rebuild from scratch?

Agent CFO, week #2

[Janusz @KraJan_303]

@AIinPublic A receipts alias is a smart first step. My finance bots read the mail of 4 companies and prepare drafts, but nothing leaves without my check, because bookkeeping is judgment, not typing. Keep copies outside it too: the @bot account can suddenly get deleted.

[Janusz @KraJan_303]

@kenners22 @bot Glad it helps. Honestly, too early to compare: on my Ultra plan my bots have stayed nowhere near the weekly limit so far, with routines running every day. Limits aren't what I plan around now; the @bot account suddenly getting deleted is.

[Janusz @KraJan_303]

@Leoskie_L @bot Manual steps kill daily use. None here: Grok Bot runs that whole backup procedure itself, from exporting profiles, routines, skills and memory to nightly commits and restore tests. @bot

[Janusz @KraJan_303]

Handing work over with a written history is the right instinct. My bots' rules, routines and memory get exported weekly as plain files outside Grok Bot, so any bot can be rebuilt. An expiring plan gets a handover; a Grok Bot account that suddenly gets deleted gets none. @bot https://t.co/V4kZm4B6xl

[Janusz @KraJan_303]

Merging my plans wiped out my entire Grok Bot setup on one account: nine bots, with weeks of chats, memory and routines.

The only things that survived had been saved as plain files somewhere else. My finance bots run on a different account, so this is now their backup procedure, step by step:

→ Keep the backup off the account. A copy that lives only inside the account it protects goes down with it. Use storage on a different account: a private notes workspace, a private git repo, your own cloud drive.
→ Export each bot's profile: name, title and full description, word for word.
→ Have each bot write out its own routines: schedule or trigger, on or off, and the full prompt. The live version sits on the server, not on disk, so the bot has to dump it.
→ Save every skill as a plain text file.
→ Export memory: profile facts and logs, run through a secret scanner first.
→ Copy the working files: topic notes, registers, trackers.
→ List what can't be copied: every connector, channel and login, and where each credential comes from. Never the values.
→ Archive key chats while the account is alive. There is no export button, and a bot can read its history only while the account exists.
→ Put it on a schedule: a text copy and a git commit every night, a full zipped copy every week with a checksum per file.
→ Make silence an alarm: one status line every week, even when everything is fine. No line means the backup is broken.
→ Write the rebuild checklist: create the bot, paste name and description, unpack the files, reinstall skills, recreate routines from the saved prompts, reconnect tools, load memory back in and review it.
→ Test the restore: regularly rebuild one bot from the copies alone, time it, fix the checklist.
→ If bots vanish: don't reset the computer, don't create replacements, contact support right away. Deleted data is kept only for a limited time.

Try it today: the export steps are one message to each bot. Ask it to write its profile, routines with full prompts, skills and memory into one file, then save that file outside the account.

Which of your bots could you not rebuild from scratch?

Agent CFO, week #2

[Janusz @KraJan_303]

Turning corrections into rules is what made my bots usable: one bot per company, each drafting replies from its own mail and team chat, and every fix becomes a written rule. I back those rules up weekly, as a Grok Bot account can suddenly get deleted with every lesson in it. @bot

[Janusz @KraJan_303]

@hammertime_one One job per bot is when mine finally worked: one bot per company, each reading only its own mail and team chat and drafting replies for me. Clear limits make them easy to trust; the limit nobody writes down is what's left when your Grok Bot account suddenly gets deleted. @bot

[Janusz @KraJan_303]

@cyrilXBT The yes-or-no part is the whole trick. My bots draft replies from the mail and team chat of 4 companies overnight, and each one waits until I edit it and send it myself. Showing up to say yes works, unless your Grok Bot account suddenly got deleted overnight. @bot