Skip to main content
Initialize Entire in a Git repository. This installs the necessary Git hooks to capture AI coding sessions.
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.

Flags

Use --yes for non-interactive setup flows:
To add another agent after initial setup, run entire agent add AGENT_NAME. --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.
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, activity, experts, and cloud dispatch — have nothing to return. Publish by creating an Entire repository or mirroring a GitHub repository. Use these flags for non-interactive setup: