Work
One Notion page per bot: computer is scratch, Notion is the brain
A bot computer can reset or roll back — important state on the box can vanish.
What hurt
@ducksays warns that a Grok Bot computer can be reset or rolled back to an older save (safer after a recent update, still risky). Pattern: every bot gets its own Notion page as shared brain (CMO logs posts, household tracks buys, CWO tracks workouts…). The computer stays scratch space. Tip only. Not affiliated with xAI.
What to install or create
Connect Notion → one page per bot → write anything that must survive there → treat box as scratch.
Bots
No new bot. Follow the first-run steps.
Plugins
Notion
Required
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/ducksays/status/2115812323872944430 (credit @ducksays).
- 2Connect Notion to each bot that holds lasting state.
- 3Create one Notion page (or DB row) per bot; name it after the role.
- 4Tell each bot: anything that must survive a computer reset lives on that page — the box is scratch only.
- 5Verify by asking one bot to append a log line, then confirm it in Notion yourself.
Approval fence
Fence deletes and schema changes as Ask-first; you can read every page too.
What to tweak
Steal page-per-bot durability. Reset cannot touch Notion.
Source
duck says @ducksays · 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.