Git for AI Agents
Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.
Want to reach these readers? Sponsor an issue.
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents.vcs.i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session.just like git did for code, i think we are the same core capabilities with ai agentsso...i developed an open source solution for that (currently supporting claude code)would love to get feedback, contribution or maybe other ideas or solutions you find for those problems.
HN · launched May 8, 2026 · 129 upvotes (top 6%) · 0 views
Niche: version control and updater software · 34 launches, 2 in the last 7 days · Explore this niche →
Category and tags
- Horizontal
- Dev tools
- Developer
- AI-native
- Commercial product
Visit website ↗ Source listing ↗
More like this: all 34 launches in version control and updater software →
Could you build this?
Partial Wrapping standard git commands and diff trees is easy, but capturing, indexing, and reasoning over agent execution context and multi-turn prompt chains requires non-trivial event-sourcing design.
What it would actually take: The product requires a daemon or CLI layer intercepting agent execution hooks, storing prompt snapshots, tool-call logs, file system mutation diffs, and AST states into an immutable event log or specialized Git branch tree. The difficult element is building an efficient context-replay and indexing system that allows semantic queries ('why did the agent delete this file?') over complex multi-agent reasoning trajectories.
Discussion
20 comments analyzed.
Competitors mentioned: jj (Jujutsu VCS), TFA's approach, Claude Code, regent-vcs
Concerns raised: High token/context cost with Claude Code, Git history pollution from frequent commits, Overhead of committing each agent action, Git protocol misuse for large contexts, Only supports Claude Code currently
Feature requests: Support for other major LLM models beyond Claude, Read-only restriction during planning phase, Edit-only restriction to planned tools in implementation phase, Integration with Jujutsu VCS workflow
Competitors
Other products that read as similar to this one : 2066 launches clear the similarity bar, closest 8 shown.
Attention rank: #161 of 2067 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).
Launched 191 days after the earliest competitor.
- Tracking AI Code with Git AI · hn · 2025-11-10 · 6 upvotes · similarity 0.66
- Agentgit · hn · 2026-09-18 · 10 upvotes · similarity 0.63
- git-lrc · hn · 2026-06-16 · 9 upvotes · similarity 0.62
- Instantly get the transcript from the agent that wrote any line of code · hn · 2026-09-03 · 5 upvotes · similarity 0.60
- Legit, Open source Git-based Version control for AI agents · hn · 2026-01-09 · 9 upvotes · similarity 0.59
- Claudit · hn · 2026-02-11 · 7 upvotes · similarity 0.57
- Git why · hn · 2026-04-11 · 11 upvotes · similarity 0.56
- AVP · ph · 2026-10-26 · 76 upvotes · similarity 0.55
The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.