Entire Integration
Overview
This document describes how to integrate Entire (AI session tracking for Git workflows) and configure a Waydev commit hook within a repository.
1. Entire Setup
1.1 What is Entire?
Entire (https://docs.entire.io/introduction) integrates with your Git workflow to capture AI agent sessions during development. These sessions are indexed alongside commits, enabling:
- Traceability of code generation
- Searchable history of AI-assisted development
- Better auditability of changes
1.2 Installation
You can install Entire using one of the following methods:
Option A: Shell Script
curl -fsSL https://entire.io/install.sh | bashOption B: Homebrew
brew tap entireio/tap && brew install entireio/tap/entire1.3 Enable Entire for a Repository
To enable Entire in a dedicated repository:
entire enable --local --skip-push-sessions --telemetry=false1.4 Configuration Verification
After enabling, verify the configuration files inside the .entire directory.
File: .entire/settings.json
{
"enabled": false
}File: .entire/settings.local.json
{
"enabled": true,
"strategy_options": {
"push_sessions": false
},
"telemetry": false,
"commit_linking": "always"
}Notes:
enabled: trueinsettings.local.jsonensures local activationpush_sessions: falseprevents session data from being pushed remotelytelemetry: falsedisables analytics collectioncommit_linking: alwaysensures sessions are always tied to commits
1.5 Check Current Status
To verify that Entire is running correctly:
entire status2. Waydev Commit Hook Setup
2.1 Purpose
The Waydev hook enables tracking of commits and developer activity for analytics and reporting.
2.2 Setup Steps
Step 1: Add Hook File
Create or copy the wd_commit_hook file into the .githooks folder.
Step 2: Configure Git Hooks Path
Run the following command to enable the custom hook:
git config core.hooksPath .githooks3. Validation Checklist
Ensure the setup is correct by verifying the following:
- Entire is installed:
entire --version - Repository is enabled:
entire status .entire/settings.local.jsoncontains the correct configuration.githooks/wd_commit_hookexists and the git hooks path is configured correctly
4. Notes & Best Practices
- Use local settings (
settings.local.json) for environment-specific configuration - Keep telemetry disabled if working with sensitive repositories
- Regularly check
entire statusto ensure sessions are being tracked - Store
.githooksin the repository for team-wide consistency
Updated 21 days ago