The Git Forge for Agent-Human Collaboration
lizziepika
55 points
35 comments
October 26, 2026
Related Discussions
Found 5 related stories in 150.0ms across 10,677 title embeddings via pgvector HNSW
- The bridge to agent-scale Git infrastructure Klaster_1 · 59 pts · October 21, 2026 · 73% similar
- TrueForge – The open-source agent harness qiasl2 · 19 pts · August 20, 2026 · 63% similar
- Agent-talk: Enabling coding agents to work together xhluca · 48 pts · July 16, 2026 · 61% similar
- Git at Any Scale meetpateltech · 30 pts · August 18, 2026 · 61% similar
- OpenAI Forked Git on GitHub rahlokzero · 23 pts · July 11, 2026 · 61% similar
Discussion Highlights (9 comments)
aboreddev
the interesting bit isnt the hosting, its the implied claim that the PR stops being the right unit of review once agents write most of the code. i think thats actually right. PRs assume the author can explain the diff. with agent code the diff is cheap and the “why” is gone the second the session closes. then bisect lands on some commit 6 weeks later and all you have is a commit msg the agent wrote for itself. sticking the session on the commit is a reasonable answer to that, tho i doubt anyone opens those during review, you’d only ever look during an incident.
rkarthik1993
Field CTO at Entire, so obviously biased. Rather than write an essay about why we built this, I’d rather just answer whatever you’re skeptical about. Happy to get into the actual mechanics: how sessions get attached to commits (it’s git refs, not a side db), what the 89x push number does and doesn’t mean, where the context/token savings fall apart, who can read whose session transcripts, how you’d migrate off if you hated it, whatever. The one thing I’ll say up front: The bet is that once agents write most of the code, the PR stops being the right unit of review, because the diff is cheap and the “why” vanishes when the session ends. Everything else follows from that. Ask away, I’ll be in the thread for a while.
Haimantika
The change we were all waiting for!
stryan
The graph generator looks interesting, but the rest of the blog post is filled with so much marketing it's a slog to get through to the good bits. I struggle to imagine a scenario where I willingly choose the "Trails" view even if, and god help us if it is, that's the direction PR review is going.
shepherdjerred
I see nothing about pricing I would happily try this out if it were going to be free for the next 1-2 years, or if I knew that the upcoming bill would be reasonable
alexzhues
I've been using entire for the last month and can't recommend it enough-- very impressed with the team behind it and hope others will give it a try.
bestcodes
I've been using Entire for a while now (specifically checkpoints, but also testing Trails more recently) and there's no going back! It's amazing!
2001zhaozhao
Very cool. I think a focus on AI code review and continuous knowledge graph synthesis are both right directions, and any system that provides the infrastructure to automatically handle these tasks eventually must do the job of a Git Forge, even if it runs locally. I am tackling the problem from a different direction, but I think there's a lot here to be inspired by.
infogulch
Lots of movement in the SCM space recently. Entire (this post) DeltaDB (by Zed) https://news.ycombinator.com/item?id=49187256 Git 3.0 / SHA-256 https://news.ycombinator.com/item?id=49924179 Anthropic Scion https://news.ycombinator.com/item?id=50073633 East River Source Control / jj https://news.ycombinator.com/item?id=49525297 Cursor Origin https://news.ycombinator.com/item?id=49334209 Radicle https://news.ycombinator.com/item?id=48147603 Probably more. I wonder what besides LLMs are driving this.