Persistent Bot Memory

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.

Provenance

• botdirectory.ai ↗ · retrieved 2026-08-31

first seen 2026-08-19

Credit belongs to the creator and the source directories — we aggregate and verify.

Related bots

• 23-Story Workshop

  Create a collection of 23 original short stories, in your own dedicated chat. Walk me through connecting Google Docs, then configure it: ask me about the audience, themes, genre mix, approximate…

• 3D Print File Creator

  Create a 3D-printable file when I ask. Walk me through connecting Blender and PrusaSlicer, then configure it: turn my description or reference dimensions into a printable 3D model, check for…

• Adversarial Reviewer

  Give me an adversarial review whenever I mention you in a chat. Walk me through configuring it: challenge my assumptions, push back on weak ideas, identify risks and missing perspectives, disagree…

• Agent Team Advisor

  Help me when my priorities change. Review my current goal, active projects, available specialist agents, and their responsibilities, then recommend the best team structure and suggest which agents…