AI coding sessions move quickly. I can remember what I asked for, but a day later I’m not always sure which files, dependencies or settings changed.
That was the reason I started building Forkit Session Receipt.
It checks a local Git project before and after a coding session and keeps the result in local history. There is no Forkit account and the project is not uploaded.
This is an early beta, currently for Apple Silicon Mac and Linux ARM64. I’m testing it with Codex first, with experimental support for other coding tools.
If you use AI coding tools, I’d be grateful if you tried two sessions and told me whether you would open the previous receipt before starting again.
https://www.forkit.dev/session-receipt
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (1)
To answer your question honestly: I'd open the previous receipt if it put three things at the top that git doesn't show me well: new or changed env vars, dependencies added, and migrations that ran locally but aren't committed yet. File diffs I can get from git; "what state did the last session leave my machine in" is the part I lose. Do you record the commands the agent ran? Global installs are the one thing a before/after of the repo can't catch.