March 1, 2026
Ship code, spill the chats
If AI writes code, should the session be part of the commit?
Coders clash over stapling AI chats to your code — receipts or revolt
TLDR: git‑memento lets developers attach AI chat transcripts to each code change for transparency and debugging. The community is split between “commit the receipts” fans who want accountability and skeptics who say Git isn’t the place—raising big questions about blame, provenance, and how we document AI’s role in our work.
A new tool called git‑memento just dropped, and the comments instantly turned into a courtroom. The pitch: when AI helps write your code, attach the whole chat as a note on the commit so future you knows what the bot was thinking. Creator mandel_x says we keep shipping AI‑assisted code but “we rarely preserve the thing that actually produced it — the session,” and the crowd had thoughts.
On one side, true believers are chanting “commit the receipts!” User burntoutgray went full retro, cheering that “the session becomes the source code,” likening today’s AI chat to the old days of peeking at the assembler to understand what really happened. Others loved the idea of documenting the why behind changes, with ramoz pushing “intent provenance” and even sharing a prototype eqtylab/y.
But the skeptics brought the spice. ares623 questioned whether Git—the tool developers use to track code—is the right place for messy AI chats at all, joking we might need a “Semi‑Human Intelligence Tracking tool” (you can do the acronym math). Meanwhile, the enterprise crowd showed up: danhergir called it a way to help companies peek inside the “LLM black box,” turning chat logs into audit trails.
So: receipts vs restraint, museum vs mailbox. Whether you see git‑memento as accountability gold or oversharing, the comments agree on one thing—AI wrote it, so someone better own the story behind it.
Key Points
- •git-memento records AI coding sessions and stores cleaned transcripts as Git notes attached to commits.
- •It supports standard commit flows, including multiple -m messages and editor-based messages, and allows amending with session note carry-over or append.
- •Notes can contain sessions from multiple AI providers and can be shared and synchronized across remotes with share-notes, push, and notes-sync.
- •The tool provides rewrite support (notes-rewrite-setup, notes-carry) to preserve provenance through rebases, squashes, and amendments.
- •Audit and diagnostics commands (audit, doctor) validate note coverage and provider configuration; providers are configurable via environment variables (Codex default, Claude supported).