re_gent CLI
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
- 805 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Local history stores code, user requests and tool results that may contain confidential data.
Install
- Works in
Manual install
brew tap regent-vcs/tap
brew install regentInstalls re_gent CLI through Homebrew on macOS/Linux. Then run `rgt init` in the project whose activity should be retained.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Local history stores code, user requests and tool results that may contain confidential data.
This is third-party code. Review the repository files before installing.
What it does
re_gent records agent actions in a separate project history. Each tool-using turn creates a step containing a workspace snapshot and the cause of the change. A source line can be traced to its step and user request. Different agent conversations have their own history branches, with shared ancestors deduplicated. The CLI shows logs, sessions and the full context of a selected change. This provides an additional activity trail between ordinary Git commits.
Who it is for. For developers who need to understand an agent’s changes and recover context after a failed refactor.
Good fit when
- Find the request that led to a changed line.
- Separate activity from several sessions working in one project.
- Inspect intermediate steps between commits while investigating a regression.
- Read the conversation and tool calls behind a selected step before resuming.
Not a fit when
- Policy forbids local copies of conversations and source fragments.
- You need a shared remote Git server with team access control.
- You require automatic support for every external tool and agent.
Example request
Show the agent request behind this changed line and which other files the same step touched.Limitations
Automatic tracking is documented for Claude Code, Codex and OpenCode; other agents need separate verification. Run `rgt init` in each intended project so its activity enters history. File snapshots, prompts and tool responses can contain secrets; inspect `.regent/` and recipient permissions before sharing the repository. This history is separate from normal commits and does not replace project backups, so continue saving important changes through your usual process.
How to disable. Stop sessions using the integration and disable its agent hooks. `.regent/` contains history; preserve needed data before removing it.
FAQ
How do I trace one source line?
Use `rgt blame src/file.go:42` with the relevant file and line. It links the line to a session, tool and prompt.
How do I inspect a full step?
Run `rgt show <step-hash>` to see the change and conversation context for that identifier.
Where is history stored?
In the project’s `.regent/`, containing content-addressed objects, session references and a SQLite index.
How do I filter history by conversation?
Use `rgt log --session claude_code:claude-20260502-143021`, replacing the identifier with one from `rgt sessions`.
Do I need to commit each action manually?
No. The integration captures turns automatically after project initialization. Normal repository commits remain a separate activity.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI replays Git changes as typing animations to present commits and working-tree edits in the terminal.
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
lazygit is a terminal Git interface for bisecting regressions: mark good and bad revisions while locating the faulty commit.
Code graph and project memory in one Rust program: the agent gets excerpts with file and line citations
A code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
A CLI and skill that record an agent's goals, decisions and rejected paths in Git so the next agent does not repeat them
README in short
History is stored in `.regent/`, separately from normal Git commits. A project example shows how these steps help trace a billing regression after refactoring.