agenttrail vs re_gent
The two are close in size: 922 stars for agenttrail, 801 for re_gent. Over the days we have tracked them agenttrail moved +106.3% and re_gent +2.4%, so agenttrail is growing faster right now.
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Provides a local, real-time observability map of coding agents' plans, tool calls, and file edits without any cloud service, account, or telemetry.
- Stars
- 922
- Tracked growth
- +106.3%
- Maturity
- ●●●●●
- Last commit
- 41d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Free, local
Provides content-addressed, per-step audit trails and per-line 'blame' tied to the exact prompt and conversation that produced a change—something traditional VCS and most tools do not track.
- Stars
- 801
- Tracked growth
- +2.4%
- Maturity
- ●●●●●
- Last commit
- 109d ago
- Language
- Go
- License
- Apache-2.0
- Cost to run
- Free local CLI; external model/API usage may incur costs
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | agenttrail | re_gent |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-repo analysis | ●●●●● Workspace snapshot |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Minimal signals | ●●●●● Ignore & dedupe |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Repo-level config | ●●●●● Config file & hooks |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Fully local | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multi-provider | ●●●●● Known providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command start | ●●●●● One-command init |
Which one to pick
Pick agenttrail if…
Privacy-first — run with one command to get a local, read-only live dashboard of agent plans and file activity bound to 127.0.0.1 with no external telemetry.
Pick re_gent if…
Agent-auditability — pick re_gent when you need a zero-config, local audit trail that shows which prompt wrote each line and lets you inspect full step and conversation context.
What people want from each one
sodiumsun/agenttrail
regent-vcs/re_gent
Questions people ask
Is agenttrail better than re_gent?
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work. agenttrail is worth picking when privacy-first — run with one command to get a local, read-only live dashboard of agent plans and file activity bound to 127.0.0.1 with no external telemetry.
Which of agenttrail and re_gent keeps my code private?
agenttrail: Fully local (5/5). re_gent: Self-hostable (4/5).
What does each one cost to run?
agenttrail: Free, local. re_gent: Free local CLI; external model/API usage may incur costs.
Full profiles: sodiumsun/agenttrail and regent-vcs/re_gent. Everything else in Observability & tracing.