cd /news/developer-tools/how-to-enable-entire · home topics developer-tools article
[ARTICLE · art-97374] src=dev.to ↗ pub= topic=developer-tools verified=true sentiment=· neutral

How to Enable Entire

Entire, a tool that captures the context behind AI-assisted code changes and links it to Git history, has introduced a new setup process. Developers can enable Entire by running 'entire enable -y' from the root of their Git repository, which installs hooks and creates project configuration to capture session context. New setups default to storing checkpoints under 'refs/entire/checkpoints/', while existing repositories can continue using the branch-based approach.

read2 min views1 publishedAug 14, 2026

Entire captures the context behind AI-assisted code changes and connects it to your Git history.

It preserves details such as prompts, tool calls, file changes, and session transcripts as checkpoints. A checkpoint is a versioned record of the work completed during an agent session, linked to the Git commit that resulted from it.

Here’s how to enable Entire and prepare your repository for its first checkpoint.

From the root of your Git repository, run:

entire enable -y

The -y

flag accepts the default setup options, including enabling Entire for all supported coding agents.

Entire installs the necessary hooks and creates its project configuration. These hooks capture the context from your agent sessions and connect it to your commits.

New setups use Git refs by default, storing each checkpoint independently under:

refs/entire/checkpoints/

Entire also supports storing checkpoints together on a dedicated branch:

entire/checkpoints/v1

Both approaches keep your session history separate from your working branch, so transcripts and checkpoint metadata do not clutter your code commits.

To select the branch-based option explicitly, run:

entire enable -y --checkpoint-backend branch

Existing repositories using entire/checkpoints/v1

can continue using it, while new repositories use the refs-based approach by default.

If you want to review the setup options and choose which agents to connect, run:

entire enable

Entire will guide you through the configuration process.

You can also select a checkpoint storage option explicitly:

entire enable --checkpoint-backend refs

Or:

entire enable --checkpoint-backend branch

Once setup is complete, check the repository’s status:

entire status

You’ll see which agents are connected, where checkpoints will be synchronized, and whether any agent sessions are active.

After you work with an agent and create a Git commit, you can view the resulting checkpoints with:

entire checkpoint list

Your repository is now ready to capture the context behind your agent-assisted work.

For a complete walkthrough, visit our Quickstart. If you are working with sensitive repositories, review Entire’s security and privacy documentation.

Happy trails!

── more in #developer-tools 4 stories · sorted by recency
── more on @entire 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/how-to-enable-entire] indexed:0 read:2min 2026-08-14 ·