How to Use Entire Git Forge: The Beginner's Guide

CodexFuse Team · 2026-11-02T15:16:50.455Z · 12 min read min read

Entire, Thomas Dohmke's agent-native Git forge, replaces the pull request with Trails. A beginner walkthrough of the Checkpoints CLI, Trails, repo mirroring, continuous memory, and credit billing.

What Is the Entire Git Forge, Exactly?

The Entire Git forge — Entire (Dohmke's company) — is the agent-native code-hosting platform launched on October 26, 2026 by Thomas Dohmke, the former GitHub CEO. The short definition: it is a git forge rebuilt for teams where AI coding agents do most of the typing. It keeps full git compatibility, but it swaps the pull request for Trails, adds a git-compatible hosting layer tuned for speed, and stores agent intent — prompts, reasoning, transcripts — alongside the code in continuous memory. Here is the mental-model lesson to carry through everything below, stated once: Entire keeps git compatibility but swaps the pull request for Trails and stores agent intent with the code.

Entire arrived with serious backing. Dohmke raised a $60M seed round in February 2026 at a $300M valuation, led by Felicis with Madrona, Basis Set Ventures, and Microsoft's M12, and runs a roughly 50-person fully remote team. If you know GitHub's beginner guide, think of GitHub as the human-typing forge lane and Entire as the agent-native git lane — the two are never rivals on this page, just different tools for different workflows. And if your agents already run through GitHub Copilot, the Entire Git forge is where that workflow graduates from "agent in your editor" to "agents across your whole repo."

How Do You Use Entire Git Forge, Step by Step?

The fastest honest way to learn the Entire Git forge is the Checkpoints CLI first, the hosted forge second. Checkpoints work in any Git repo with no account at all — the hosted forge (Trails, distributed hosting, cloud memory) needs a login. Seven steps:

1. Install the Entire CLI. On macOS or Linux, run curl -fsSL https://entire.com/install.sh | bash (or brew install --cask entireio/tap/entire). On Windows, irm https://entire.com/install.ps1 | iex. The CLI is open source under the MIT license.
2. Capture agent sessions with entire enable. In any Git repo, run entire enable, pick your agents, and Entire installs its agent hooks and git hooks. Every commit that involves agent work gets a checkpoint — the prompts, the transcript, and the files touched — linked by an Entire-Checkpoint commit trailer. No account needed for session capture.
3. Log in. Run entire login to connect the CLI to your Entire account.
4. Mirror a GitHub repo (or go native). Run entire repo mirror add for the guided mirror wizard, or entire repo create laksa --project hawker for a native repo. Mirroring keeps GitHub as your source of truth while Entire adds Trails on top.
5. Open your first Trail. From the CLI, entire trail create --title "Your feature here". Entire spins up review agents that score every push on quality, security, and slop.
6. Read the scores, clear the findings, approve. Each review agent submits a score and rationale. Address the findings with your agents or by hand, then entire trail approve once the Gates — human approvals plus passing CI — are satisfied.
7. Merge and query the memory. entire trail merge closes it out. Later, entire search and entire blame tell you which checkpoint and prompt produced any line of code.

curl -fsSL https://entire.com/install.sh | bash
cd your-repo
entire enable        # no account needed — captures agent sessions locally
entire status        # see what's hooked up
entire login         # connect to the hosted forge
entire repo mirror add   # wizard: mirror a GitHub repo
entire trail create --title "Add rate limiting to the API"

What Are Trails, and How Do They Replace the Pull Request?

Trails are Entire's replacement for the pull request, and they are the single biggest idea in the Entire Git forge. A pull request is a human-readable diff with a conversation attached. A Trail is a head-up display with automated, customizable evals scored by agents on every push. The lifecycle runs in three steps. First, spin up: a Trail starts from a bug report, a feature request, or straight from an agent — and unlike a pull request, a Trail can span multiple repositories. Second, scoring: each review agent runs independently in a cloud sandbox and submits a score plus its rationale; Entire shows the last five runs alongside the current one, using its own evals for Security, Slop, and Human Review Required. Third, close all findings then merge: findings carry severity levels, agents or humans can dismiss or address them, and per-repo Gates — human approvals and passing CI checks — gate the merge itself.

Under the hood, the review agents run Claude Code and Codex with the latest models on Daytona and E2B sandboxes, according to the vendor. The first-class CI integrations are Buildkite and Depot: bk pipeline convert migrates your GitHub Actions workflows, and depot ci migrate promotes them into Trails. If you have worked through a Claude Code walkthrough before, Trails will feel familiar — the same class of agent, pointed at your changes instead of your editor.

How Does Entire's Git Hosting Work?

The second primitive is a new Git-compatible source-control server: a distributed object store plus a transactional ref database, with live regions in the US, EU, UK, India, Australia, and Singapore (Singapore launched on October 29, 2026 — a week after the forge itself). It speaks Git, so your existing tools work, but the vendor claims pushes run up to 89x faster than GitHub and 6x faster than Cursor Origin, naming its benchmark ForgeMark. Report those figures as the vendor's own: Entire publishes 418 pushes per second against 65 for Cursor, 15 for Pierre, 10 for GitLab, and 4.7 for GitHub. No independent benchmark has reproduced those numbers yet, so treat them as a vendor claim, not a tested fact.

Should You Mirror Your GitHub Repo or Go Entire-Native?

The honest answer for beginners: mirror first, go native when you are ready. Mirroring installs the Entire GitHub App on a repo; GitHub stays the source of truth, pushes route back through GitHub, and Trails work on top of your existing pull requests. Entire-native branches are prefixed entire/unmirrored/, and Entire can serve clones and fetches during a GitHub outage. Native hosting is the full commitment: Entire becomes your remote, with the distributed server and its push-speed claims.

The mirror arc is the low-risk way to learn the whole platform: you keep your existing Git beginner guide habits, GitHub keeps running, and Trails add the agent review layer on top. Native makes sense when a repo is born inside an agent workflow and humans only ever review.

How Do Checkpoints Capture Your Agent's Work?

Checkpoints are the unit of Entire's continuous memory on your own machine. When you run entire enable, Entire records each agent-involved commit as a checkpoint: the prompts you sent, the model's reasoning and transcript, and the files it touched. Checkpoints are stored as their own Git refs — refs/entire/checkpoints/… — linked to your commits by the Entire-Checkpoint trailer, and pushed alongside your code. Entire never adds commits to your branch. (Early coverage described separate-branch storage; the current vendor docs describe the dedicated-refs design.)

The working set of commands is small:

entire checkpoint list          # every checkpoint in this repo
entire checkpoint explain abc123   # what one checkpoint did
entire session resume my-branch    # hand the session to an agent
entire rewind                      # step a change back
entire search "rate limit"         # hybrid semantic + keyword search
entire blame src/api.ts            # which checkpoint wrote this line
entire why src/api.ts              # which prompt produced it

One disambiguation, stated once: Inngest's "step.run Checkpoints" are a different product entirely — Inngest checkpoints are saved results of durable-execution workflow steps, and have nothing to do with Entire's agent-session checkpoints.

What Is Continuous Memory? entire-graph and entire-brain

The third primitive turns those checkpoints into a searchable memory of your repo. entire-graph maps the codebase with tree-sitter, runs locally with no network, and the vendor claims up to 71% token savings from graph-aware context — again, the vendor's own figure, not an independent test. entire-brain indexes your agent sessions onto that graph. Both are open source and local-first plugins. The payoff for beginners is entire search and entire blame: instead of asking "who wrote this and why," you ask "which checkpoint and which prompt wrote this," and get the transcript back.

Entire vs GitHub: What Actually Changes?

This is the comparison beginners actually need, and it is why "entire vs github" is one of the cluster's core keywords. GitHub is the forge for humans who type; the Entire Git forge is the forge for agents that type, with humans reviewing. Nothing about your Git knowledge breaks — the remote speaks Git — but the review model, the memory model, and the billing model all change.

How Does Entire Billing Work?

Entire bills only for agent usage, through prepaid usage credits — everything else on the forge is free. The vendor's billing docs, last updated two days before this article, set the terms: a $100 one-time trial credit per billing account, ending at $100 of usage or 90 days, whichever comes first, granted when you set up billing with a verified credit or debit card — no payment is actually taken. One important current fact: new trials are temporarily paused, per the vendor docs verbatim as of November 2, 2026. Check the docs before planning around the trial.

After the trial, the minimum credit purchase is $10 and the default top-up is $25; purchased credits expire 365 days after purchase, and card management runs through Stripe. A beginner-friendly detail: the preset project agents — risk, confidence, drift, security, review — run on free credit, so you can watch the whole Trail arc work before custom agents require billing to be set up. If you are pricing infrastructure around this, the same prepaid-credits habit you learn from what VPS hosting is applies: start small, watch the burn, top up deliberately.

7 Beginner Mistakes on the Entire Git Forge

Every one of these comes from a real beginner trap in the launch-week docs and tutorials.

Sources

• Entire — "The Git Forge for Agent-Human Collaboration" (vendor launch post, 2026-10-26): entire.com/blog/the-git-forge-for-agent-human-collaboration
• Entire Docs — "Billing" (vendor; prepaid credits and $100 trial terms): docs.entire.com/billing
• Entire — "Entire CLI" reference (vendor; MIT license, install and commands): entire.com/gh/entireio/cli
• Entire — "Code Hosting in Singapore is Now Available" (vendor, 2026-10-29; regions and project commands): entire.com/blog/code-hosting-in-singapore-now-available
• GeekWire — "Former GitHub CEO launches rival platform built for AI coding agents" (2026-10-26; funding and team): geekwire.com/2026/former-github-ceo-launches-rival-platform-built-for-ai-coding-agents/
• andrew.ooo — independent FAQ on the Entire Git forge (verified 2026-10-27): andrew.ooo/answers/what-is-entire-git-forge-dohmke-trails-2026/

Frequently Asked Questions

Is the Entire Git forge open source?

Entire is open-core: the Checkpoints CLI is open source under the MIT license, and the entire-graph and entire-brain plugins are open source and local-first. The hosted forge, review agents, and distributed hosting are the commercial product, billed in prepaid credits.

Can I use Entire's Checkpoints CLI without an account?

Yes. entire enable works in any Git repo with no account — it captures prompts, transcripts, and files touched as local checkpoints. You only need entire login when you want the hosted forge: Trails, cloud memory, and syncing.

Does Entire replace GitHub?

It can, but beginners should mirror first. The Entire GitHub App mirrors a repo with GitHub as the source of truth, adds Trails on top of your pull requests, and Entire can even serve clones during a GitHub outage. Go Entire-native when a repo is born inside an agent workflow.

How much does Entire cost?

Only agent usage is billed, via prepaid credits: minimum purchase $10, default top-up $25, credits expire after 365 days. The vendor offered a $100 one-time trial credit (verified card required, no payment taken), but new trials are temporarily paused as of November 2026 — check the billing docs for the current state.

Is Entire production-ready?

Entire launched October 26, 2026 and is available to any developer today, with six live hosting regions. It is still launch-phase software: public repositories and self-hosting are on the roadmap, not at launch. For agent-heavy new projects it is usable now; for public open-source work, keep GitHub as home base for the time being.