Quickstart

This quickstart will help you get started with Entire. You will learn how to create a checkpoint that links an agent session to a Git commit, mirror a GitHub repository on Entire, create an Entire repository, create an Entire Trail, and enable review Agents on every push. A checkpoint stores the session context behind a change, such as the prompt, agent transcript, tool calls, and changed files. A mirror keeps GitHub as your source of truth while Entire serves the repository from a region you choose.

Before You Start

You need:

Git installed and configured
A GitHub account and a repository you can access
An AI coding agent, such as Antigravity CLI, Claude Code, Codex, Copilot CLI, Cursor, Factory, OpenCode, or Pi
macOS, Linux, or Windows
Optional: GitHub CLI (gh) installed and authenticated, if you want to publish a new demo repository to GitHub

1. Install Entire

Entire ships two release channels:

stable: recommended for most users.
nightly: prerelease builds with newer changes.

Nightly is available through Homebrew, the Linux install script, and the Windows PowerShell installer. Scoop currently supports stable only.

macOS (Homebrew)
Linux
Windows
From Source

# Stable
brew install --cask entireio/tap/entire

# Nightly
brew install --cask entireio/tap/entire@nightly

# Stable
curl -fsSL https://entire.com/install.sh | bash

# Nightly
curl -fsSL https://entire.com/install.sh | bash -s -- --channel nightly

# Stable
irm https://entire.com/install.ps1 | iex

# Nightly
iex "& {$(irm https://entire.com/install.ps1)} -Channel nightly"

The script uses Scoop for stable installs when Scoop is available. See Installation for the Scoop commands and the script’s options.

go install github.com/entireio/cli/cmd/entire@latest
go install github.com/entireio/cli/cmd/git-remote-entire@latest

Check that Entire is installed:

entire version

For other installation options, see Installation.

2. Open a Repository and Enable Entire

Use an existing GitHub repository, or create a new folder for a demo.

Existing repository
New demo repository

Clone the repository, then enter it:

git clone git@github.com:OWNER/REPOSITORY.git
cd REPOSITORY

Create and enter a folder:

mkdir entire-demo
cd entire-demo

When you enable Entire in the next step, it initializes Git and creates an initial commit. It does not create or push to a remote — you publish it just after, before the mirror step.

Choose the agent you use and run its setup command:

Antigravity CLI

entire enable -y --agent antigravity

Claude Code

entire enable -y --agent claude-code

Codex

entire enable -y --agent codex

Copilot CLI

entire enable -y --agent copilot-cli

Cursor

entire enable -y --agent cursor

Factory

entire enable -y --agent factoryai-droid

OpenCode

entire enable -y --agent opencode

entire enable -y --agent pi

Entire installs hooks that capture your agent’s work and link it to Git commits. If you started from the new demo folder, publish it now. entire enable has initialized Git and made the first commit, and the mirror step needs a repository Entire can reach:

gh repo create entire-demo --source . --private --push

entire enable creates .entire/settings.json and .entire/.gitignore so collaborators share project settings. Entire keeps .entire/settings.local.json local for personal overrides.

3. Create Your First Checkpoint

Start your agent from the repository root and give it a small task:

Create a file named hello-entire.md with a short note explaining that this is my first Entire checkpoint.

When the agent finishes, commit the change:

git add hello-entire.md
git commit -m "Add first Entire checkpoint"

Entire asks whether to link the commit to the agent session:

Entire: Active <agent> session detected

Link this commit to session context?
  [Y]es / [n]o / [a]lways (remember my choice):

Press Enter or type y. You have created a checkpoint. It links the commit to the prompt, transcript, tool calls, and files from the agent session. View it with:

entire checkpoint list

Choose always at the commit prompt if you want Entire to link future agent-assisted commits automatically.

Checkpoint storage depends on the repository configuration. See Session Storage for storage and push behavior.

4. Mirror Your Repository

A mirror lets agents clone and pull through Entire while GitHub remains the upstream repository. Log in before you begin:

entire login

Also make sure the Entire GitHub App can access the repository. An organization admin may need to approve the app. Create a mirror:

entire repo mirror add

Choose your repository and the region where you want Entire to host it. Choose a region close to your agents or one that meets your organization’s data-residency requirements. Then add the mirror as a remote in this checkout:

entire repo remote add entire

Check the result:

git remote -v

There should now be an entire remote on an entire:// URL, with origin still pointing at GitHub. Fetch and push through it:

git fetch entire
git push entire

Entire sends pushes through the mirror to GitHub. Your existing GitHub access, branch protection, and review rules still apply.

To send everyday Git commands through Entire without naming a remote, point origin at the mirror instead:

entire repo remote add origin --override

--override is required because origin already exists. Entire prints the URL it replaces, and that printout is the only record of it, so copy it somewhere first if you want to restore it later.

Create a New Repository on Entire

You can now host your code on Entire. A project holds your repositories. Create a project, replacing readme with an available project name and nodo with your organization’s name:

entire project create readme --owner nodo

If you already have a project, use its name in the next command. Create a repository replacing the name documentation in the project:

entire repo create documentation --project readme

Entire waits for the repository to become active and displays its remote URL. By default, the repository uses the project’s region. Clone the repository using the remote URL from the output. For example:

git clone entire://aws-us-east-2.entire.io/et/readme/documentation
cd documentation

You can now commit changes and use git push and git pull as usual.

You can also create a repository on entire.com: open or create a project, create a repository within it, then copy the clone command from the repository page.

To learn how to do it from entire.com and an agent prompt to automate setup, see Repositories.

5. Create Your First Trail

Trails are our reinvention of a pull request. From a single project view, you can now track discussions, investigate related sessions, and make changes across multiple repositories at once. From your repository root, create your trail:

entire trail create --title "My first Entire trail"

This creates a new trail and links the current branch. Check that the trail is created:

entire trail show

Any new changes, sessions, and checkpoints in this branch will automatically be linked to your Trail. Start your agent and give it a small task:

Create a file named first-trail.md with a short note explaining that this is my first Entire Trail.

When the agent finishes, commit and push the change:

git add first-trail.md
git commit -m "Add first checkpoint in new Trail"
git push origin my-first-entire-trail

When prompted to link this commit to session context, select Y. You have now linked your first checkpoint to your new Trail! To learn more about trails, see Trails overview.

6. Create Your First Agent

After every push, Entire Agents will review the code changes and evaluate confidence levels through different customizable monitors, such as Confidence, Risk, Security, and Drift. Navigate to your project on entire.com:

Open your project and go to Agents.
You can start from a list of preset agents and click Enable as is: Or, click New agent and customize the agent to your own needs:
Under Agent, give it a name and description. Pick the harness, model, reasoning effort and timeout, and write its Instructions (what it should review). Then set the signal it reports: a value type and a polarity.
Under Trigger, choose when it runs, for example Trail branch pushed, Run manually or Recurring schedule.
Under Repositories, select at least one repository.
Leave the toggle on Active and click Create agent.

Each of these agents produces an evaluation score and can flag what needs fixing as Findings.

Continue With

Inspect Checkpoints

Review the session and decisions behind a commit.

Search Past Work

Search code, commits, and agent sessions together.

Mirrors in the CLI

Learn more about mirror regions and Git remotes.

Set Up an Agent

Configure another supported coding agent.

Getting Started

Guides

Integrations

Migration

Security

Resources

Before You Start

1. Install Entire

2. Open a Repository and Enable Entire

3. Create Your First Checkpoint

4. Mirror Your Repository

Create a New Repository on Entire

5. Create Your First Trail

6. Create Your First Agent

Continue With

Inspect Checkpoints

Search Past Work

Mirrors in the CLI

Set Up an Agent

​Before You Start

​1. Install Entire

​2. Open a Repository and Enable Entire

​3. Create Your First Checkpoint

​4. Mirror Your Repository

​Create a New Repository on Entire

​5. Create Your First Trail

​6. Create Your First Agent

​Continue With

Inspect Checkpoints

Search Past Work

Mirrors in the CLI

Set Up an Agent

Before You Start

1. Install Entire

2. Open a Repository and Enable Entire

3. Create Your First Checkpoint

4. Mirror Your Repository

Create a New Repository on Entire

5. Create Your First Trail

6. Create Your First Agent

Continue With