BOTUnclaimed

Persistent Bot Memory

by TheCraigHewitt·0.0(0 saves)·8 uses

Persistent Bot Memory is a Grok Bot setup that uses GitHub.

Open @thecraighewitt on X Compare

Facts

What it is, what it does, what it needs.

What it is: Bot
What it does: Persistent Bot Memory is a Grok Bot setup that uses GitHub.
Works with: Grok
Setup: In Grok Bot, create a new agent and connect GitHub. Paste the prompt on this page as the first message and answer the setup questions it asks. Do one supervised run, then save the bot for reuse. Keep any spend or send behind your approval.
Source: https://x.com/TheCraigHewitt

Capabilities

GitHub

Starter prompt

Prompt

Persist 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.

Use withGrok

via @thecraighewitt