Now that agents are writing so much code, Entire is trying to reinvent the coding platform itself:
AI has sped up the pace of coding, putting new demands on infrastructure and changing how developers work. Entire, a developer platform from former GitHub CEO Thomas Dohmke, aims to be the solution to those changes.
The platform, available for use today, is built on Entire’s decentralized Git network, announced in July, which is designed to withstand the sharp increase in AI coding activity that has caused mounting GitHub outages.
Entire aims to be “a GitHub alternative for the speed that teams require to merge changes as fast as coding agents create them,” the company said in its announcement. The new git forge aims to make human-agent coding work more seamless by redesigning several features developers have become accustomed to. Here’s how it works.
The first change Entire makes to the standard coding experience is that it replaces pull requests with what it calls Trails.
“Unlike the classic Pull Request model of reviewing code changes with a diff, Trails offer developers a heads-up display similar to an airline pilot, with customized evals that are scored by agents on every code push,” the company said.
“All data is available not only on Entire's web interface, but also through the open-source Entire CLI. This allows coding agents to address findings in a loop, while the human developer validates the progress. When all evals are satisfied, they can merge the code without needing to look at the code itself.”
Entire said that the agents running this process are customizable, and each trail shows how agents are spending tokens.
"With Trails, Entire treats the idea, the agent trace, and the outcome of a developer's sessions as first-class artifacts for review alongside the code,” Dohmke said. “It uses multiple agents to generate evals that verify the quality and success of AI-generated code to let developers confidently merge without reviewing every line in the diff."
The company also claims it offers Git hosting “up to 89x faster than GitHub” and six times faster than Cursor origin, thanks to that aforementioned decentralized network. The platform lets developers create, migrate, and host private repositories in multiple locations across the world, currently starting with the US, India, Australia, and the EU.
Another differentiating factor is Continuous Memory, which keeps developer session logs next to code in the repo as a data source. Agents can use them to search for answers, which, Entire said, helps them use up to 71% fewer tokens. This is similar to other memory features in AI chatbots that reduce time spent gathering context by using past conversations or other agent interactions, where provided, to speed query response time. Entire said Continuous Memory is made up of a codebase graph and an “agentic brain” that uses previous sessions and prompts as lessons so agents don’t repeat mistakes.
Entire is available to try today for all developers.
(Score: 2) by JoeMerchant on Monday November 02, @04:19AM (4 children)
Completely wrapped doesn't mean completely protected, you can cover some negative cases but never all of them.
>one/two order of magnitude better test coverage
Three or four for me, I'm old-school - barely ever wrote unit tests in the past.
>one absolutely can hit the budget limits for testing (we've hit them twice in the past 7 years - no more physical room for in-house test farms followed by blowing past the budget for the cloud CI infrastructure).
Yikes, we're much less resource intensive, our build server of the past 10 years is a fanless Core i7 box - we bought a newer faster box to replace it a couple of years ago but inertia has left the old one as the main build server still today. A full system build takes about 30-40 minutes, including tests. More tests won't be sinking the new server anytime soon.
🌻🌻🌻🌻✌️ [google.com]
(Score: 2) by c0lo on Monday November 02, @07:09AM (3 children)
Ours takes about 20 mins, except that our build makes use of Ninja build [ninja-build.org] on top of SN-DBS (sony distributed building system) with 200+ dev workstations (pretty beefed up each) enrolled to take part on spare CPU/IO time (which is plenty when you're just coding or incrementally build your changes locally or sleeping into your timezone). There are 10+ builds in the same time, almost all the time except the weekend.
Ahem... our yearly budget for CI is in the 8 figures territory. A full test round takes about 8 hours, including the test data "cooking" (generating/transforming once the test assets into formats that are consumable at the level of unit/functional tests).
https://www.youtube.com/@ProfSteveKeen https://soylentnews.org/~MichaelDavidCrawford
(Score: 2) by JoeMerchant on Monday November 02, @01:49PM (2 children)
>A full test round takes about 8 hours, including the test data "cooking"
Yeah, that's my idea of "real testing." All the cool kids think that a unit test should execute in under 100 milliseconds and on the server instead of the target hardware - I ask them: what's the point of having unit tests that miss problems? They just say "it's too expensive to do that kind of testing." I go check the amount of my last direct deposit and sigh... it isn't good for job security to call your colleagues idiot moron children.
🌻🌻🌻🌻✌️ [google.com]
(Score: 2) by c0lo on Monday November 02, @02:14PM (1 child)
When one hits one's head on the reality enough times, the reality ends seeping into the head through the cracks. It's usually called growing up (or old. Why not both, actually? Because some never grow up and finish professionally dead. Or managers, but I repeat myself)
Now, to be honest, with the test data set being all cooked, about 80% of our unit tests execute under 100 millies, with the maximum (of the rest) being under 5 seconds. Except that we literally have them for execution in the millions.
(I don't know why I keep using "we/ours", 2 weeks ago I quit with the intention to retire early)
https://www.youtube.com/@ProfSteveKeen https://soylentnews.org/~MichaelDavidCrawford
(Score: 2) by JoeMerchant on Monday November 02, @03:13PM
> 2 weeks ago I quit with the intention to retire early
Congrats, I hope...
I still refer to my first job (1991-2003) as we/our.
🌻🌻🌻🌻✌️ [google.com]