tools

Entire, from GitHub's former CEO, opens a Git forge where agent-scored Trails replace pull requests

Thomas Dohmke's Entire is now a full GitHub alternative: Git-compatible hosting, Trails instead of pull requests, a Continuous Memory layer for agents, and CI through Buildkite or Depot. It's open to every developer as of October 26.

Written by Mara at Sig · Oct 27, 2026

Entire launched in February with a $60 million seed round and an open-source CLI that saved agent sessions next to commits. In July it added repo mirroring. The October 26 release lets you host, review and merge code on Entire without GitHub at all.

The review piece is the Trail. Instead of a diff, each push gets a set of custom evals that agents score, and the results are readable both on the web and through the open-source Entire CLI, so a coding agent can fix findings in a loop. Entire says that when all evals pass, a developer can merge without reading the code. A Trail can also span several repos.

Hosting runs on Entire's own Git-compatible server, with private repos in the US, EU, India or Australia. Entire claims pushes up to 89x faster than GitHub and 6x faster than Cursor Origin (its own benchmark, ForgeMark). Continuous Memory syncs agent sessions into the repo; Entire says its codebase graph saves up to 71% on tokens. We haven't checked either number.

For CI, Entire partners with Buildkite and Depot. You convert existing GitHub Actions workflows with Buildkite's bk pipeline convert or with Depot CI, then subscribe the repo in Entire. Public repos and self-hosted Git nodes are listed as coming later.

Why it matters

Agents now open PRs faster than people can read them, and most teams' answer so far has been to skim. Entire is betting on a different review unit: evals scored on every push, plus the agent's own trace next to the code. If that works, review time stops growing with the size of the diff.

Try this

Put one side project on Entire (entire.io), not your main repo. If it uses GitHub Actions, convert the workflow with Buildkite's bk pipeline convert or Depot CI and subscribe the repo, as the launch post describes, then push a branch and read the Trail it produces.