Do you just let your AI agent read the git log to catch up on changes?
by•
Project files usually explain what an app does, but they don't really tell the AI what actually changed since yesterday.
I'm trying to figure out the best way to give an agent context on recent updates without feeding it a massive wall of text every time.
13 views
Replies
I'd have the agent leave a short note at the end of each session: what changed, what's still open, and the next command to run. Start the next session with that note plus `git status` and the recent diff; the commit log rarely says why the work stopped.
Honestly, I'm a bit surprised myself at how well it works. Here's the setup:
A global CLAUDE.md every project inherits, plus one per project.
A memory folder per project. The agent writes down what I corrected and why, anything it changed in production, incidents and their causes, and anything that took over 30 minutes to figure out. Only the index loads at the start, one line per memory.
A worklog saved automatically every day, so nobody has to remember to write it.
A session card saved automatically, so if a session hangs, the next one picks up from there.
93 incident notes, each linked from the rule it created.
So the next session never reads the git log. It reads what mattered.