Show HN: Git for AI Agents

A new Hacker News project called re_gent is pitching itself as version history for AI coding assistants — basically, a way to see what the bot changed, which instruction caused it, and eventually roll things back when the machine goes full chaos mode. In plain English: if your AI helper wrecks your code and you’re left muttering, “it was working five minutes ago,” this tool wants receipts.

But the real show was in the comments, where admiration quickly collided with classic internet skepticism. One camp was instantly sold. “This is brilliant,” wrote one commenter, already asking how broadly it could work. Another gave it the cautious parent review: cool idea, but now comes the hard part — can it handle side features, branching work, cleanup, and all the messy real-world stuff? That mood was basically: love the concept, prove it survives contact with reality.

Then came the spicy backlash. The hottest jab was a brutally simple one: why are all these “X for agents” tools acting like the original X doesn’t already exist? In this case, X is Git, the long-time tool people already use to track code changes. Another commenter basically said, uh, agents can already use Git and even search old chat sessions if you tell them to. Translation: some readers saw invention, others saw reinvention with a shinier label.

So yes, the product is about audit trails for AI. But the comments turned it into something juicier: a referendum on whether AI needs brand-new tools, or whether people are just forgetting the old ones while adding extra drama to the workflow.