Guides

AI Checkpoints

AI Checkpoints

The AI Checkpoints report lets you track distinct AI checkpoints across commits, compare periods, and review checkpoint-level usage with repository and team context. It is accessible under AI Impact in the left sidebar.

📘

A checkpoint captures an AI coding session in full. As an AI agent runs — whether Claude Code, Cursor, Copilot, etc. — the session is recorded in the background. When the developer runs git commit, a permanent checkpoint is created and its ID is attached to the commit as a trailer (Entire-Checkpoint: ...). Session data is stored in the entire/checkpoints/v1 branch and pushed alongside the code, keeping a complete, auditable record of every AI-assisted change.

The top of the page displays four summary metrics:

  • Total checkpoints - The total number of AI checkpoints recorded in the selected period.
  • Avg AI attribution - The average percentage of code attributed to AI across all checkpoints.
  • Avg tokens per checkpoint - The average number of tokens consumed per checkpoint.
  • Active repositories - The number of repositories with AI checkpoint activity.

Each metric also shows a percentage change compared to the previous period.

Checkpoints - A paginated table listing all commits with AI checkpoint metadata for the selected filters and period, with the following columns:

  • Checkpoint ID - The unique identifier of the checkpoint, linked to the commit.
  • Repository - The repository where the commit was made.
  • Commit message - The commit message, linked to the commit in the source provider.
  • Author - The developer who made the commit.
  • AI agent - The AI tool used for the checkpoint (e.g. Claude Code).
  • AI tokens - The number of tokens consumed for this checkpoint.
  • AI Attribution - The percentage of the commit attributed to AI, shown as a progress bar and percentage.
  • Files Changed - The number of files modified in the commit.
  • AI Changed Lines - The number of lines changed by AI.
  • Human Changed Lines - The number of lines added, unchanged, or removed by the developer, shown as additions, modifications, and deletions.
  • Created Date - The date and time the checkpoint was created.

Filters available at the top of the report include date range, Repos, Attributes, Teams, Groups, Agent, and Settings.

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. 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 .githooks

3. 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

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 status to ensure sessions are being tracked
  • Store .githooks in the repository for team-wide consistency

Updated 20 days ago