Refresh memory before the daily report
Each morning, your bot re-reads your source-of-truth docs, drafts the memory updates for your OK, then writes the daily report so nothing stale leaks in.
For owners whose daily AI report quietly drifts out of date as the business's real documents change · Grok Bot · Beginner
Researched, not run yetWhat that means
Copy the prompt
Fill in the [brackets] after you paste it.
Every morning at [TIME], before you write the daily report:
1. Re-read these source-of-truth docs: [LIST 3 TO 5 FILES OR LINKS].
2. Tell me what changed since yesterday, in one short list.
3. Draft the memory updates: what to add, fix, or drop. Do not apply them until I say yes.
4. Then write the daily report using the docs you just read, not your memory, and mark any line you could not confirm from them.
If a doc is missing or unreadable, say so in the report instead of guessing. Do not change the docs themselves, and do not update memory until I approve the changes.Copied. Paste it into Grok Bot next.
Free PDF
Get this setup as a PDF
Enter your email and a print-ready copy of this setup opens here, to save as a PDF. The free starter pack opens too. Tap confirm in the email that follows to get occasional new setups. Unsubscribe anytime.
Already a subscriber? Unlock it on this device
Free PDF
A confirmation email is on its way too: tap confirm in it to get new setups by email.
Three ways to run this setup
Free
Copy and paste it yourself
Copy the prompt above into ChatGPT, Claude or Grok. It drafts. You approve.
Go to the prompt$9 once
Complete Pack
One payment, no membership. Opens the pack pages: Bot Safety Checklist, Second Brain Starter Vault, Voice File Starter, Tested Grok Bot prompt pack, Write it as code prompts.
See the Complete PackFree to start, VIP $19 a month
Save it as a bot in the guided setup app
The app turns this setup into a bot with the draft-only rules. 3 setups build free; the rest are part of VIP. A human reviews a prompt or setup for you within 24 hours, up to 2 a month.
Build it in the app
Want this one tested next? Vote for it.
What you get back
Illustrative. Your results will differ.
- Memory refresh, 6:55 AM: 2 changes found (new price sheet, procedures doc moved).
- Daily report, 7:00 AM: built from refreshed docs. 1 line marked unconfirmed.
- Gap flagged: knowledge folder unreadable, section skipped instead of guessed.
3 steps
- Copy the prompt.
- Paste it into Grok Bot.
- Fill in the [brackets], then read the answer before you send or use it.
Quick answer
A Bot keeps lasting rules and facts in memory, but your files move faster than memory updates. The fix is one morning routine with two steps in order: re-read your named source-of-truth docs and draft what should change in memory, then write the daily report from the docs just read, not from memory. The memory updates apply only after you approve them. If a source is missing, the report says so instead of guessing.
How do you set it up?
Tools
- Grok Bot
- Three to five named source-of-truth docs (memory doc, knowledge folder, procedures doc)
- One morning routine scheduled before report time
Steps
- Name the sources of truth: one memory doc, your knowledge folder, your procedures doc. Three to five files; a longer list never gets read.
- Keep standing facts in docs, not chats. The docs note a Bot saves lasting rules and facts to memory when you ask, and a dated source-of-truth doc is what every bot reads first.
- Add one morning routine that runs before your report time, with the prompt below: re-read the named docs, list what changed, draft the memory updates, then write the report. You approve the updates before they apply.
- Make honesty structural: if a doc is missing or unreadable, the routine reports the gap. xAI's routine guidance says to report the failure instead of using old data.
- Weekly, compare memory against the docs and prune what drifted. The memory cleanup setup on this site is the companion for that pass.
Where to paste this prompt
Grok Bot → paste the prompt into a chat, or save it as a routine or scheduled task if the job repeats
More ways to run it
Which chat tools work with this prompt?
This prompt needs routines and connectors, so it's written for:
- Grok Bot
How sure is this?
Last updated: · Last reviewed:
Before you use this
What it is allowed to do: Drafts for you. Writes drafts (emails, posts, plans, replies). You review and send. Nothing goes out without you.
At a glance: time, cost and difficulty
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Drafts for you
Writes drafts (emails, posts, plans, replies). You review and send. Nothing goes out without you.
- Time saved (estimate)
- Not measured yet
- Difficulty
- Beginner
- Tools needed
- Grok Bot
- Typical cost
- Prices: Not stated in sources.
Reviewed Nov 3, 2026
Basis (estimate): No timing claim: the sources describe memory and routines, not minutes saved.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- A doc list that grows past five files, so the refresh gets shallow.
- Letting the routine edit the source docs. It reads and reports; you edit.
- Treating memory as the source of truth. Memory is a cache; the docs are the record.
What tips make it smoother?
- Order is the whole trick: refresh first, report second. One routine, two steps, always in that sequence.
- Mark unconfirmed lines in the report instead of deleting them. The gaps show you which doc is slipping.
- If you move assistants later, the Import Memory tool in settings carries preferences over.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read xAI’s write-up (docs.x.ai)
xAI: What a Bot remembers: a Bot saves lasting rules, preferences, facts and a dated log of work when asked; logins and cards belong in Vault, not memory (read 2026-11-03)
- Read xAI’s write-up (docs.x.ai)
xAI: Create a routine: confirm the schedule, the input source, and what should happen when a source is missing; the example instruction is to report the failure instead of using old data (read 2026-11-03)
- Read xAI’s write-up (docs.x.ai)
xAI: Import Memory brings preferences and context from another AI assistant into Grok Bot memory (read 2026-11-03)
Common questions
- Why would my daily report go stale?
- The bot reports from what it remembers, and memory updates lag the real files. A refresh step before the report is what closes that gap.
- Can one routine do both steps?
- Yes, and it should: the order is what matters. Re-read and update memory first, then write the report from the refreshed view.
- What if a source doc is missing one morning?
- The report should say so. xAI's routine guidance is explicit: report the failure instead of using old data.
Free kit by email
Get the free kit by email
The starter pack and the Portable AI Office, sent to your inbox. New setups by email after that. Unsubscribe any time.
What to do next
- Clean up your agent's long-term memory
Review your AI agent's long-term memory monthly, delete stale facts, date the ones you keep, and stop task details from leaking into new work.
- One source-of-truth doc every bot reads
Keep one short, dated document of current facts and decisions that every bot reads before starting, so bots stop forgetting and contradicting each other.
- Audit your bot instructions every week
Keep a fleet of bots honest about what they were told, with a weekly check that flags instructions that slipped or conflict.
Have a setup that works? Submit it. We credit sources and write it up in plain language.