Developer Install

Coding agent telemetry — prompts, session traces, AI authorship data — exists on developer machines. Installing Git AI on every developer laptop enables collection of this telemetry from every agent session automatically.

There are two ways to distribute Git AI to developers:

• Share an install link — best for PoCs and small teams
• Distribute via MDM — best for enterprise-wide rollouts

For a proof-of-concept evaluation, start with an install link for the first 10–20 engineers. Switch to MDM distribution when rolling out to the full organization.

Share an Install Link

Best for PoCs and small teams.

Log in to the Git AI dashboard and click Invite Developers on the Contributors page. This generates a permanent invite URL that can be shared in a document, email, Slack message, or any other channel.

When a developer opens the link:

1. The developer authenticates with GitHub, GitLab, or Bitbucket
2. Git AI verifies the developer is a member of the connected SCM organization
3. A unique, one-time install command is generated for that developer

The install command configures Git AI and sets up agent hooks on the developer's machine. Once complete, telemetry from every supported coding agent begins flowing to the dashboard.

Distribute via MDM

Best for enterprise rollouts.

For large-scale deployments, use an MDM (Mobile Device Management) solution to install Git AI across the organization without requiring each developer to run a manual install.

Requirements

Installation Steps

Place the git-ai binary on each developer machine. The default location is:

• Unix/Linux/macOS: $HOME/.git-ai/bin/git-ai
• Windows: %USERPROFILE%\.git-ai\bin\git-ai.exe

The binary is a platform-specific download from GitHub Releases (e.g. git-ai-macos-arm64, git-ai-linux-x64, git-ai-windows-x64.exe). On macOS, remove the quarantine attribute after downloading:

xattr -d com.apple.quarantine $HOME/.git-ai/bin/git-ai

Reference install scripts that automate this:

• Unix/Linux/macOS: install.sh
• Windows: install.ps1

After installing the binary, run:

git ai install-hooks

This sets up integration with supported IDEs and AI coding agents (Cursor, VS Code with GitHub Copilot, etc.). Once complete, telemetry from every supported coding agent begins flowing to the dashboard.

Optional: Wrap Git

Wrapping git by placing git-ai on the user's PATH is optional. If you wrap git, developers will see an AI authorship summary after every commit:

[hooks-doctor 0afe44b2] wsl compat check
 2 files changed, 81 insertions(+), 3 deletions(-)
you  ██░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ai
     6%             mixed   2%             92%

This adds a small ~10–20ms overhead per wrapped git command.

Configuration File

Create $HOME/.git-ai/config.json (or %USERPROFILE%\.git-ai\config.json on Windows) with organization settings. See Enterprise Configuration for the full option reference.

{
    "ignore_prompts": false,
    "allow_repositories": [
        "https://github.com/yourorg/*"
    ]
}

Tracking Installation

The Contributors tab in the Git AI dashboard shows the status of every developer across the organization:

• Sign-up status — whether each developer has installed Git AI, filtered by "Signed Up", "Not Signed Up", or "All Contributors"
• Agent integrations — which coding agents are installed and collecting telemetry (e.g. Cursor, Claude Code, GitHub Copilot)
• Installation errors — any failures encountered during setup appear here with diagnostic details

If a developer encounters an installation error, the Git AI team helps debug the issue and carries learnings forward to the MDM installer configuration so the same problem does not affect other engineers.