Re Gent
Version-Control for AI coding agents.
Last verified:
What is Re Gent?
Re Gent is re_gent is version control specifically built for AI coding agents. It tracks what your AI coding assistant changes, why it made those changes, and lets you blame, log, and rewind agent activity. Unlike Git which tracks human commits, re_gent captures every tool call an AI agent makes—edits, file writes, bash commands—automatically without requiring manual commits.
The tool stores agent history in a `.regent/` directory alongside your `.git/` directory, using content-addressed storage with BLAKE3 hashing and a SQLite index for sub-10ms queries. Key commands include `rgt log` for step-by-step agent activity history, `rgt blame` to see which prompt wrote each line of code (not which human committed it), `rgt show` for full context including code changes plus the conversation that produced them, and `rgt sessions` to view all concurrent agent sessions at a glance.
re_gent is designed for developers using AI coding assistants like Claude Code, OpenAI Codex CLI, and OpenCode. It is particularly valuable for teams running multiple AI agents in production, debugging agent-generated code, and maintaining audit trails for compliance. The tool complements Git rather than replacing it, filling the gap between "the agent committed some code" and understanding every prompt, tool call, and decision that produced it.
The tool is open-source (Apache License 2.0), written in Go, and includes a VSCode extension with inline blame annotations and session timeline view. It supports tracking multiple concurrent agent sessions with separate session branches and automatic deduplication.
Re Gent pricing
Pricing model: Freemium
Free and open-source under Apache License 2.0. No paid plans or tiers advertised. Available via Homebrew (macOS/Linux), Go install, or from source. The tool is currently in public alpha.
Re Gent pros
- Automatically captures every AI agent tool call without manual commits
- rgt blame traces any line of code back to the exact prompt that generated it
- Tracks full conversation context alongside code changes
- Supports multiple concurrent agent sessions with separate branches
- Content-addressed storage with BLAKE3 hashing ensures data integrity
- SQLite index enables sub-10ms query performance
- Open-source and free to use under Apache License 2.0
- Written in Go for fast, reliable performance
- Works with Claude Code, Codex CLI, and OpenCode out of the box
- Hooks auto-configure on rgt init with zero manual setup required
- VSCode extension provides inline blame annotations in editor
- Survives /compact and /clear commands that normally erase agent memory
- Automatic deduplication prevents redundant history entries
- Gitignore-compatible with .regentignore support
- Homebrew installation available for macOS and Linux
- DAG structure per session enables proper version history tracking
Re Gent cons
- Currently in public alpha, not yet production-ready for compliance processes
- Only tracks file-level changes, not external API or database side effects
- Supported tools limited to Claude Code, Codex, and OpenCode only
- Cursor, Cline, Continue, and Aider integration still planned not available
- Rewind feature is still in development not yet implemented
- No built-in session sharing or merge support yet
- No garbage collection or integrity verification features currently
- Does not replace Git, requires using both tools together
- VSCode extension must be installed separately from CLI
- Cannot prove agent-generated code is correct, only trace its origin
Frequently asked questions about Re Gent
What is re_gent?
re_gent is version control for AI agents. It tracks what your AI coding assistant changes, why it made those changes, and lets you blame, log, and rewind agent activity. It captures every tool call an AI coding agent makes automatically, storing history in a .regent/ directory with content-addressed storage and SQLite indexing.
Does re_gent replace Git?
No, re_gent complements Git, it does not replace it. Git tracks human commits while re_gent tracks agent activity at the prompt level. Use both together—Git for code versioning and re_gent for agent audit trails with prompt-level attribution.
Which AI coding agents does re_gent support?
re_gent fully supports Claude Code, OpenAI Codex CLI, and OpenCode. Integration with Cursor, Cline, Continue, and Aider is planned for future releases. Hooks auto-configure on rgt init with no manual setup required for supported tools.
How does rgt blame work?
rgt blame traces any line in your codebase back to the specific prompt that caused it to be written. While Git blame tells you who committed a line, rgt blame tells you which prompt generated it, including the session ID, tool name, and full conversation context. This is useful for debugging when an agent produces a subtle bug.
What is the difference between rgt log and rgt show?
rgt log displays step-by-step agent activity history showing what files changed, what tools were used, and when. rgt show displays full context for a specific step including the tool call, file changes, and the complete conversation that produced the change.
How does re_gent handle multiple concurrent agents?
re_gent tracks multiple concurrent agent sessions as separate session branches with automatic deduplication. Each agent gets its own session ref, and you can use rgt sessions to view all active sessions at a glance. You can also filter rgt log by session using --session flag.
Where is re_gent data stored?
re_gent stores agent activity in a .regent/ directory alongside your .git/ directory. The structure includes objects/ for content-addressed blobs with BLAKE3 hashing, refs/ for session pointers, index.db for SQLite query index, and config.toml for configuration.
Can I rollback agent changes with re_gent?
re_gent lets you inspect and understand agent changes, and a rgt rewind feature to restore the workspace to any previous step is in development. Currently you can see what changed and which prompt caused it, but full non-destructive rewind functionality is on the roadmap.
Is there an editor integration for re_gent?
Yes, there is a VSCode extension that provides inline blame annotations showing which step modified each line, hover tooltips with full step context, a session timeline view in the sidebar, and one-click access to conversation history. The CLI must be installed and rgt init run in your project first.
How do I install re_gent?
You can install re_gent via Homebrew on macOS/Linux with 'brew tap regent-vcs/tap' followed by 'brew install regent', or via Go with 'go install github.com/regent-vcs/regent/cmd/rgt@latest', or from source by cloning the GitHub repository and building with Go. Homebrew installation automatically sets up shell completions.