When should you use it?
- You learn a lot in chats and lose it
- You keep notes in GitHub repos
- Assistant memory feels unreliable
Not for: Private material you would not store in a hosted repo; People without a GitHub workflow
What do you need, and what do you get?
You need
- GitHub connector with access to chosen repos
- An AGENTS.md per repo
You get
- Summary files per topic
- A growing catalog of decisions and ideas
How does it work, step by step?
- Pick the reposLimit access to a few repos meant for notes.
- Write AGENTS.mdExplain in each repo where summaries go, naming rules and which index files to update.
- Add a standing instructionTell the assistant to read the right AGENTS.md at the start of a session.
- Ask for a write-upAfter a useful exchange, ask it to summarize and commit the file to the right repo.
- Reference past notesList key files in AGENTS.md so later sessions build on them.
The prompt
Our own prompt, inspired by mindcrime on Hacker News and written to work in ChatGPT and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Summarize what we just discussed about {topic} as a markdown note. Read AGENTS.md in {repo} first and follow its rules for location and naming. Include: key points, sources mentioned, open questions. Commit the file and add a line to the index. Show me the diff before committing.
Inspired by mindcrime on Hacker News: Hacker News comment on keeping AI conversations in git repos. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Give access only to notes repos, not code you ship.
- Summaries can drift from what was said; skim before committing.
Our take
Built-in chat memory is opaque; a git repository is not. This setup gives you notes you own, with history, that any assistant can read when pointed at them. The AGENTS.md convention does the steering. Limit the assistant to a few repositories meant for notes, never code you ship. In each one, an AGENTS.md explains where summaries go, how files are named and which index files to update, and a standing instruction tells the assistant to read it at the start of a session. After a useful exchange, ask for a write-up and skim it before it is committed, since summaries can drift from what was actually said. Listing key files in AGENTS.md lets later sessions build on earlier notes instead of repeating them. Private material you would not store in a hosted repository should stay out. Because everything lives in git, you get history, diffs and the option to move the notes to another assistant later, which built-in chat memory does not offer.
Where the time goes back: Explanations you would otherwise lose become searchable files that future sessions can read.
FAQ
Why not rely on built-in memory?
Was setup hard?
Source and credit
Inspired by mindcrime on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on keeping AI conversations in git repos
- Creator
- mindcrime on Hacker News
- Published on
- Hacker News
- Original date
- Oct 17, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.