Top
Best
New

Posted by doshay 1 day ago

Show HN: Git for AI Agents(github.com)
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents.

vcs.

i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session.

just like git did for code, i think we are the same core capabilities with ai agents

so...

i developed an open source solution for that (currently supporting claude code)

would love to get feedback, contribution or maybe other ideas or solutions you find for those problems.

110 points | 60 commentspage 3
keybored 23 hours ago|
None of these X-for-agents seem to motivate why they don’t use X.
tfrancisl 23 hours ago|
Git is a particularly egregious one, imo. It has a simple cli and solves all of the problems presented here! Worktrees for "exploratory" work that you might throwaway, and otherwise atomic commits just make tracking changes and reasoning for changes easy.
alansaber 23 hours ago||
I am all for extremely granular control of agents. Good work.
grim_io 20 hours ago||
What's git for AI agents? git. What's a browser for AI agents? a browser. What's a Flux Capacitor for AI agents? a Flux Capacitor. You get the point.
Abhijeet620380 19 hours ago||
Nice project. The interface feels clean and fast.
throwatdem12311 22 hours ago||
can’t you just make agent hooks that do this with plain git?
doshay 1 hour ago|
that's exactly what i tried in the first place, but i think it would be misuse of git protocol, git is built for files - the blobs/ tree calc & mechanism , for large contexts and linear thinking flow it's differnt, but honestly - i think you can get to a very good solution with pure git..
User23 13 hours ago||
I'm really pleased how wildly all the other commenters are misunderstanding this.

I was counting on this concept as competitive advantage.

But since the algorithm isn't going to surface me anyhow, for giggles I'll say I'm leaning more toward darcs than git.

boombapoom 22 hours ago||
my agent rebased and forcepushed with conflicts...
wxw 21 hours ago||
Fun idea! There's frankly a lot to learn from reviewing agent sessions.
kolinko 22 hours ago||
hm, I can’t find the link?
doshay 1 hour ago|
https://github.com/regent-vcs/re_gent
_blk 23 hours ago|
Cool idea. Time will tell how it matures. It doesn't look trivial. Definitely should beat my current "scan the history" approach. Couple questions arose while reading the README:

- Would it integrate with rtk? Rtk is a token saver that shortens native output of got (and other) commands. - Does it track feature branches? - Is there garbage collection when history is rewriting (rebase before PR or removal of credential files.. ) or "simplification" of data as it gets older (Claude session logs lost...)?

Wishing you all the best with the project.

More comments...