Entire CLI
Entire is a Git forge built for agent–human collaboration. This CLI is how you and your agents use Entire from the terminal — anything you do on entire.com, you can do here:
- Distributed Git hosting — host repositories on Entire's Git-compatible server, or mirror your GitHub ones, and replicate them in regions around the world for data residency and the scale of agent traffic. → Repositories & Git Hosting
- Trails — instead of reviewing a diff, get a heads-up display for every change, with customizable evals that agents score on every push. → Trails
- Continuous memory — capture every agent session as a checkpoint linked to your commits; entire-brain combines them with entire-graph's code map into project memory. → Agent Sessions
Works with Claude Code, Codex, Cursor, Copilot CLI, OpenCode, Antigravity, Factory AI Droid, Pi, and more, and extends through plugins. Pushes through a GitHub mirror still trigger your GitHub Actions, and Trails can also show CI results from Buildkite and Depot.
Open source under the MIT license. Docs: docs.entire.com.
Contents
Install
brew install --cask entireio/tap/entire # macOS and Linux
curl -fsSL https://entire.com/install.sh | bash # macOS and Linux, without Homebrew
irm https://entire.com/install.ps1 | iex # Windows PowerShell 5.1+
For the nightly channel (prerelease builds with the latest changes):
brew install --cask entireio/tap/entire@nightly
curl -fsSL https://entire.com/install.sh | bash -s -- --channel nightly
iex "& {$(irm https://entire.com/install.ps1)} -Channel nightly"
Requires Git on macOS, Linux, or Windows. Scoop, go install, and installing during a GitHub outage are covered in Installation.
Quick Start
1. Capture agent sessions — works in any Git repository, no account needed:
cd your-project
entire enable # pick your agents; installs their hooks and Entire's git hooks
entire status # current sessions and where checkpoints are uploaded
2. Put a repository on Entire — sign in, then mirror a GitHub repository into one or more clusters, or create an Entire-native one. Mirroring needs the Entire GitHub App installed for that repository.
entire login
entire repo mirror add # wizard: pick repos and clusters
entire repo clone /gh/<owner>/<repo> --nearest
entire project create # wizard: owner, name, region
entire repo create <name> --project <project>
entire repo clone /et/<project>/<name>
Then cd into the clone and run entire enable there to capture sessions in it.
3. Open a Trail — in a repository on Entire, on the branch you're working on:
git switch -c add-rate-limiting
entire trail create --title "Add rate limiting"
entire trail show
Repositories & Git Hosting
Entire hosts Git repositories on clusters in several regions, so agents can clone, fetch, and push against a copy near where they run.
- Region — where an organization's or project's data stays: a jurisdiction such as
us or eu, set with --region when you create it.
- Cluster — an Entire Git host, such as
aws-eu-central-1.entire.io. entire cluster list shows them; a repository can have copies on several.
- Project — holds Entire-native repositories and belongs to an organization or a personal account. Repository and project commands take its plain name (
--project acme); Trail commands take et/<project>, and treat a GitHub owner as the project for its mirrors (gh/<owner>).
- Mirror — a copy of a repository on one cluster. GitHub repositories are mirrored from their GitHub upstream, and native repositories can be mirrored to more clusters.
entire repo mirror manages both.
Repository references name their forge: /et/<project>/<repo> for an Entire-native repository, /gh/<owner>/<repo> for a GitHub mirror, or a full entire://<cluster>/… clone URL.
entire repo create web --project acme # Entire-native, private by default
entire repo mirror add /gh/acme/web --cluster aws-us-east-2.entire.io,aws-eu-central-1.entire.io
entire repo clone /gh/acme/web --nearest # time each cluster and use the fastest
entire repo remote add entire # add Entire to an existing checkout, beside origin
A GitHub mirror keeps GitHub as the source of truth: clones and fetches come from Entire, and pushes are forwarded to GitHub, where your GitHub permissions, branch protection, and required checks still apply. Clones use entire:// URLs through the git-remote-entire helper that ships with the packaged installs; after that, it is plain Git.
See Repositories and Mirrors in the CLI for regions, mirroring, unmirrored branches, moving a mirror off GitHub, branch protection, and access.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
