LearnGrok← Grok Bot directory
ProductivityGitHub
Persistent Bot Memory
A bot definition mirrored from botdirectory.ai, contributed by TheCraigHewitt. Read it before you run it: it was written by someone else and is not reviewed here.
The prompt
Set up a new bot that persists knowledge from my bots to one GitHub repo. Chat memory dies when the thread ends. Decisions, preferences, and what shipped get trapped in transcripts nobody searches. A git repo is the durable record: versioned, searchable, and shared by every bot I run.
Walk me through connecting GitHub. Ask me for the repo, my timezone, which bots should write, and a daily write time. Then set it up like this:
- One folder per bot.
- Each bot writes one markdown file per day (`YYYY-MM-DD.md`).
- Log only decisions, shipped work, and standing preferences.
- Never log secrets, tokens, passwords, customer data, or private messages.
- If nothing happened that day, stay quiet.
- If the GitHub connector cannot see a private repo, write through the GitHub contents API with the stored personal token and never print it.
Do one supervised first write I approve, then save the daily schedule.- Contributor
- TheCraigHewitt
- Added upstream
- 2026-08-19
- On botdirectory.ai
- https://botdirectory.ai/bots/persistent-bot-memory/
More bots for these tools
Mirrored 2026-08-20. A bot brief tells software what to do on your behalf. Check what it asks for access to before you hand it any.
More in Productivity
Sponsored
