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 and Waydev Commit Hook using Waydev Git-Hooks & AI Telemetry Installer

Important notes about Entire configuration (see more below - Data privacy):

• session data is never pushed remotely
• analytics collection is disabled
• work sessions are always tied to commits

1.3 Check Current Status

To verify that Entire is running correctly:

./install-wd.sh --diagnose

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.