What is Re_gent?

Re_gent is version control built specifically for AI agent activity. While Git tracks file changes, Re_gent tracks the conversations and prompts that produced those changes. It captures every action your coding agent takes, shows you exactly which prompt caused each modification, and lets you undo, blame, checkout, or replay agent work across multiple sessions. Think of it as Git for your AI agent's actions — a complete audit trail that keeps you in control.

Who it's for

• AI-assisted developers who want to understand exactly what their coding agent changed and why, without digging through messy chat logs
• Engineering teams using multiple agents who need to work in parallel without conflicts, reviewing and merging agent work like they would with human contributors
• Quality-conscious programmers who need to roll back agent changes safely, trace bugs to specific prompts, and maintain a clean codebase even when agents make mistakes

Key features

Session-level logging with rgt log

Re_gent shows you the full conversation that led to each change. Instead of a vague "fix bug" commit message, you see the actual prompt that triggered the modification. Every agent action is recorded with its context, making it easy to understand why something changed.

Blame for AI agents with rgt blame

Every line of code is traced back to its exact prompt. If three different agent sessions touched the same file, Re_gent shows you which prompt from which session caused each change. This gives you a complete audit trail across multiple agent interactions.

Parallel agent sessions with rgt sessions

Each agent conversation gets its own branch, allowing multiple agents to work simultaneously without collisions. You can review and merge their work just like you would with human developers, keeping everything organized and conflict-free.

Content-addressed storage for full history

Even when AI tools like Claude compact or delete messages, Re_gent preserves the complete record in content-addressed storage. You never lose the audit trail, no matter what the agent does to clean up its own history.

What stands out

"Git tracks files. Re_gent tracks the agent conversations that produced those files."

This distinction is the core of Re_gent's value. Traditional version control treats code changes as isolated events, but modern AI development is conversational. When an agent breaks something, Re_gent doesn't just show you the broken code — it shows you the exact prompt that caused the breakage and lets you rewind both the code and the conversation. It's infrastructure designed for a world where AI agents write most of the code.

Worth checking out if…

You use AI coding assistants like Claude Code, Codex, or OpenCode and want more control over what your agents do. If you've ever wondered "what did my agent actually change?" or needed to undo a specific agent action without losing unrelated work, Re_gent gives you that power. It's especially valuable for teams running multiple agents in parallel, or anyone who wants a reliable audit trail for AI-generated code. Best of all, it's free forever under the Apache-2.0 license and open-source on GitHub.