A CLI version control system (686 GitHub stars) that stores AI agent activity in .regent/ — conversations, tool calls, and reasoning — enabling git-style blame, log, and rewind for agent sessions.

Why is Git not good for AI-generated code?

Git tracks file diffs but not why a change was made or which agent prompt produced it. When an AI agent rewrites a function, the commit only shows the result, not the reasoning chain.

How do you audit what an AI coding agent did?

re_gent stores every agent action in a content-addressed SQLite index under .regent/. You can run `regent log`, `regent blame`, or `regent rewind` to trace exactly what the agent changed and why.

Does re_gent replace Git?

No. re_gent complements Git: Git tracks file state, re_gent tracks agent conversations that produced those files. Use both in the same repo.

← Back to dashboard

clawsmith.com/signal/version-control-audit-trail-ai-agent-actions

⚠ IssueWide OpenLive

Git Doesn't Track AI Agent Reasoning — Devs Building Dedicated Audit-Trail VCS for Agents

Git tracks files but not why an agent changed them. re_gent (686 GH stars, HN Show HN 129pts/67c) stores agent conversation history alongside code in .regent/, giving blame/log/rewind on agent sessions. 'Why Git is no good for AI-generated code' HN thread hit 110+ pts. Problem: multi-agent codebases are unauditable.

Product Idea from this Signal

A CLI tool that stores AI agent conversation history inside your git repo so you can blame, log, and rewind agent reasoning sessions alongside code diffs

1.1k ▲

Git tracks what files changed but not why an AI agent changed them. In multi-agent codebases, a file diff is meaningless without the conversation that produced it: you cannot audit which prompt triggered a decision, you cannot rewind to before the agent took a wrong turn, and you cannot compare two agents' reasoning on the same task. re_gent (686 GitHub stars) proved the demand by shipping a .regent/ directory that stores agent conversation history alongside code, but it is an early open-source project with no paid layer and limited VCS integration. This CLI tool embeds agent conversation history directly into the git object store on every commit, exposes standard git commands (blame, log, diff, rewind) that surface the agent's reasoning at any revision, and charges teams for the audit and compliance reporting layer on top.

CLIVERSION-CONTROLAI-AGENTSAUDIT-TRAILGITDEVTOOLCOMPLIANCE

Competitive33 leadsView Opportunity →