> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.com/llms.txt
> Use this file to discover all available pages before exploring further.

# enable

> Initialize Entire in a Git repository. This installs the necessary Git hooks to capture AI coding sessions.

Initialize Entire in a Git repository. This installs the necessary Git hooks to capture AI coding sessions.

```bash theme={null}
entire enable [flags]
```

If Entire is not yet configured, this runs the full configuration flow. If Entire is already configured but disabled, this re-enables it. In a directory that is not a Git repository, see [Bootstrap a New Repository](#bootstrap-a-new-repository).

## Flags

| Flag | Description |
| - | - |
| `--absolute-git-hook-path` | Embed full binary path in Git hooks. Required for GUI Git clients that don't source shell profiles. See [GUI Git Clients](/guides/configuration/git-hooks#gui-git-clients). |
| `--agent NAME` | Agent to set up hooks for: [`antigravity`](/agents/antigravity), `claude-code`, `codex`, `opencode`, `cursor`, `copilot-cli`, `factoryai-droid`, `pi`, or an `entire-agent-<name>` executable that follows the [Agent Integration Protocol](/agents/agent-integration-protocol/overview). Runs without prompts. |
| `--agent-help-skill` | Install the Entire agent-help Skill, which points agents at [`entire agent-help`](/cli-reference/agent-help), for the selected agents. |
| `--checkpoint-backend BACKEND` | Set checkpoint storage to `refs` (one Git ref per checkpoint) or `branch` (one shared branch). A first-time setup uses `refs` when you omit the flag. |
| `--checkpoint-push-remote NAME` | Git remote that receives checkpoint uploads. Saved to `.entire/settings.local.json`, even with `--project`. Mutually exclusive with `--checkpoint-remote`. Without it, Entire asks which remote to use only during first-time interactive setup, without `--agent`, and only when more than one remote is eligible; `--yes`, `--skip-push-sessions`, and `--checkpoint-remote` skip the question and leave automatic election in place. |
| `--checkpoint-remote PROVIDER:OWNER/REPO` | Push checkpoint data to a separate repository. `PROVIDER` is `github` or `gitlab`, as in `github:org/checkpoints-private`. See [Checkpoint Remote](/guides/checkpoints/store-checkpoints-in-another-repo). |
| `-f, --force` | Force reinstall hooks (removes existing Entire hooks first) |
| `--import-history` | During first-time setup, import the selected agents' existing session history from the last 30 days without prompting. See [`entire import`](/cli-reference/import). |
| `--local` | Write settings to `.entire/settings.local.json` instead of `.entire/settings.json`. |
| `--project` | Write settings to `.entire/settings.json` even if it already exists |
| `--search-skill` | Install the Entire search Skill for the selected agents. See [`entire search`](/cli-reference/search). |
| `--skip-push-sessions` | Disable automatic pushing of session logs on Git push |
| `--telemetry` | Enable anonymous usage analytics (default: true) |
| `-y, --yes` | Accept defaults without prompting. Useful for automation, CI, and bootstrap flows. |

Use `--yes` for non-interactive setup flows:

```bash theme={null}
# Non-interactive setup for a specific agent
entire enable --yes --agent claude-code

# Non-interactive setup using default choices
entire enable --yes
```

To add another agent after initial setup, run [`entire agent add AGENT_NAME`](/cli-reference/agent#agent-add).

`--yes` is not just a confirmation bypass. It runs `entire enable` non-interactively with default choices. On a fresh repository, it enables the default setup without prompts. On an already configured repository, it follows the setup-management path. Outside a Git repository, it also accepts the bootstrap defaults to initialize Git and create the initial commit.

Important behavior:

* If you also pass `--agent NAME`, that explicit agent selection takes precedence over the default multi-agent behavior.
* If you pass `--telemetry=false`, or set `ENTIRE_TELEMETRY_OPTOUT`, that explicit telemetry opt-out still overrides the `--yes` default.
* `--yes` does not import existing agent history. Add `--import-history` when you want the last 30 days of transcripts imported too.

> [!NOTE]
>
> The `--local` and `--project` flags control which Entire settings file is modified. Entire always modifies the agent's **project** settings (e.g., `.agents/hooks.json`, `.claude/settings.json`, `.opencode/plugins/entire.ts`, `.factory/settings.json`, or `.pi/extensions/entire/index.ts`).

## Bootstrap a New Repository

When run outside a Git repository, `entire enable` offers to initialize one and make the initial commit. It never creates or pushes to a remote, so publish the repository yourself when you are ready.

Until you do, the commands that read from Entire's servers — [`search`](/cli-reference/search), [`activity`](/cli-reference/activity), [`experts`](/cli-reference/experts), and cloud [`dispatch`](/cli-reference/dispatch) — have nothing to return. Publish by [creating an Entire repository](/guides/repositories/entire-native-repositories) or [mirroring a GitHub repository](/guides/repositories/mirrors). Use these flags for non-interactive setup:

| Flag | Description |
| - | - |
| `--init-repo` | Initialize a Git repository non-interactively when the directory is not one. |
| `--no-init-repo` | Exit instead of prompting to initialize a repository. |
| `--initial-commit-message MESSAGE` | Commit message for the initial commit. |
| `--skip-initial-commit` | Don't create the initial commit. |

```bash theme={null}
# Initialize a repository and commit, without prompts
entire enable --init-repo --agent claude-code

# Initialize with your own first commit message
entire enable --init-repo --initial-commit-message "Start project" --agent claude-code

# Fail rather than prompt when this isn't a repository
entire enable --no-init-repo
```