re_gent Blame for VS Code
May 6, 2026 · View on GitHub
Git-style blame for AI agent activity. See which prompt wrote each line of code.
re_gent is a version control system for AI agents—it tracks every change an agent makes, which tool call produced it, and the conversation context behind it. This VS Code extension brings that provenance directly into your editor.
Features
Inline Blame Annotations
See which step (tool call) last modified each line, right in your editor:
a1b2c3d4 • Edit • 5m ago │ function hello() {
Rich Hover Tooltips
Hover over any line to see:
- Full step hash
- Timestamp
- Tool name (Edit, Write, Bash, etc.)
- Tool arguments excerpt
- Link to full conversation context
Session Timeline
Browse your agent's step-by-step history in the sidebar:
- See all steps in chronological order
- Click any step to see the diff
- Filter by session
Conversation Context
One-click access to the full transcript that led to any change.
Installation
Prerequisites
-
Install the re_gent CLI: Follow instructions at github.com/regent-vcs/regent
# Using Homebrew (macOS/Linux) brew install regent-vcs/tap/regent # Or build from source git clone https://github.com/regent-vcs/regent cd regent go build -o rgt ./cmd/rgt -
Initialize a re_gent repository in your project:
cd your-project rgt init # Configure Claude Code hook (automatic tracking) # This modifies .claude/settings.json -
Make some changes with Claude Code so there's data to display:
- The hook will automatically capture each tool call as a Step
- After a few edits, run
rgt logto verify steps are being captured
Install Extension
From Source (Development)
-
Clone this repository:
git clone https://github.com/regent-vcs/vscode-regent cd vscode-regent npm install npm run compile -
Open in VS Code and press
F5to launch Extension Development Host -
Open a workspace with a
.regent/directory
From VSIX (Coming Soon)
- Download the latest
.vsixfrom Releases - In VS Code:
Extensions > ... > Install from VSIX... - Open a workspace with
.regent/directory
From Marketplace (Coming Soon)
- Search for "re_gent Blame" in VS Code Extensions
- Click Install
- Open a workspace with
.regent/directory
Usage
Viewing Blame
Open any tracked file—blame annotations appear automatically in the editor (if enabled).
Keyboard shortcuts:
- Hover over a line: See step details
Cmd+Shift+P→ "re_gent: Show Step" → Enter step hash
Commands
re_gent: Show Step Details- View full metadata for a stepre_gent: Show Conversation Context- See the transcript leading to a changere_gent: Refresh Blame- Manually refresh blame annotations
Configuration
Open VS Code Settings (Cmd+,) and search for "re_gent":
regent.enableInlineBlame- Enable/disable inline annotations (default: true)regent.blamePosition- Show blame in gutter or inline (default: inline)regent.sessionId- Session to show blame for (empty = most recent)
How It Works
re_gent captures every tool call (Edit, Write, Bash) that an AI agent makes. Each becomes a Step—like a git commit, but automatic and enriched with:
- The exact tool arguments
- The conversation context
- Per-line provenance (blame)
This extension reads .regent/index.db and .regent/objects/ directly to show you that provenance inline.
Architecture
- Read-only: Never modifies your
.regent/data - Fast: Direct SQLite queries + content-addressed object reads
- Safe: No subprocess calls, no git conflicts
Development Status
Current version: 0.1.0 (initial release)
- Inline blame annotations
- Hover tooltips
- Session timeline view
- Conversation context panel
- Rewind command
- Multi-session switching
- DAG visualization
- CodeLens integration
Contributing
See CONTRIBUTING.md for development setup and guidelines.
License
MIT License - see LICENSE
Links
- re_gent CLI: github.com/regent-vcs/regent
- Documentation: regent.sh/docs (placeholder)
- Issues: github.com/regent-vcs/vscode-regent/issues
Made by the re_gent team