Entire Integration

Overview

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 | bash

Option B: Homebrew

brew tap entireio/tap && brew install entireio/tap/entire

1.3 Enable Entire for a Repository

To enable Entire in a dedicated repository:

entire enable --local --skip-push-sessions --telemetry=false

1.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: true in settings.local.json ensures local activation
• push_sessions: false prevents session data from being pushed remotely
• telemetry: false disables analytics collection
• commit_linking: always ensures sessions are always tied to commits

1.5 Check Current Status

To verify that Entire is running correctly:

entire status

2. Data privacy and how Waydev reads AI attribution

2.1 What stays on the developer's machine

By design, raw AI session data never leaves the developer's machine. Prompts and AI conversation contents are not pushed to your remote, and Waydev does not need them. This is a deliberate privacy decision.

The push_sessions: false setting in .entire/settings.local.json enforces this. Session data stays local. If you prefer, you can optionally choose to push Entire session data to its own branch, but this is not required for Waydev to work.

Waydev reads AI attribution from the commit message itself, not from Entire's session branches.

2.2 How Waydev gets the attribution data

The post-commit hook (wd_commit_hook, which is open-source and readable in any editor) performs the extraction locally at commit time, then folds the result into the commit message. For each commit, the hook does the following:

• Reads the Entire-Checkpoint: <id> trailer that Entire already added to the commit.
• Resolves the session ID from the local .entire/logs/entire.log.
• Aggregates token counts from the local .entire/metadata/<session>/full.jsonl.
• Reads the dominant agent name and the computed attribution line.
• Amends the commit with a single trailer: WD: <base64>.

Decoded, that payload is just eight pipe-separated fields:

agent_name|tokens|files_touched|ai_lines|human_added|human_modified|human_removed|ai_percentage

2.3 How the data reaches Waydev

The WD: trailer is part of the commit object, so it travels with the commit on a normal git push. Waydev ingests it through its standard repository connection, exactly as it reads any other commit metadata. No session contents, prompts, or conversation logs are transmitted at any point.

I'd also suggest one small change to section 1.4: promote the privacy point out of the plain Notes bullet list so it isn't easy to miss. For example, add a callout directly under the settings.local.json block:

3. Waydev Commit Hook Setup

3.1 Purpose

The Waydev hook enables tracking of commits and developer activity for analytics and reporting.

3.2 Setup Steps

Step 1: Add Hook File

Copy the wd_commit_hook and post-commit files into your Git hooks folder.

If you already have a post-commit file, append the content of the downloaded post-commit file to it.

Step 2: Configure Git Hooks Path

Run the following command to enable the custom hook:

git config core.hooksPath .githooks	

4. Validation Checklist

Ensure the setup is correct by verifying the following:

• Entire is installed: entire --version
• Repository is enabled: entire status
• .entire/settings.local.json contains the correct configuration
• .githooks/wd_commit_hook exists and the git hooks path is configured correctly

5. Notes & Best Practices

• Use local settings (settings.local.json) for environment-specific configuration
• Keep telemetry disabled if working with sensitive repositories
• Regularly check entire status to ensure sessions are being tracked
• Store .githooks in the repository for team-wide consistency

6. Waydev Git-Hooks & AI Telemetry Installer Script

install-wd.sh is an interactive POSIX bash installer script designed to configure Waydev AI Telemetry and Git Commit Hooks across one or multiple Git repositories in a target directory.

It sets up OpenTelemetry (OTel) metrics export for supported AI agent tools (Claude Code and OpenCode), connects commits to Entire.io session tracking, and appends Waydev AI attribution metadata (WD: ... trailer) to Git commit messages.