git-ai-project/git-ai

git-ai

Git AI is an open source git extension that tracks the AI-generated code in your repositories. After installing the extension, every line of AI code is linked to the agent, model, and prompts that generated it — so you never lose the intent, requirements, and architecture decisions behind your code.

Just prompt and commit — no workflow changes:

git commit

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

git ai blame /src/log_fmt/authorship_log.rs

cb832b7 (Aidan Cunniffe      2025-12-13  133) pub fn execute_diff(
cb832b7 (Aidan Cunniffe      2025-12-13  134)     repo: &Repository,
cb832b7 (Aidan Cunniffe      2025-12-13  135)     spec: DiffSpec,
fe2c4c8 (Aidan Cunniffe      2025-12-02  136)     format: DiffFormat,
fe2c4c8 (Aidan Cunniffe      2025-12-02  137) ) -> Result<…> {
fe2c4c8 (claude              2025-12-02  138)     // Resolve commits
fe2c4c8 (claude              2025-12-02  139)     let (from, to) = match spec {
fe2c4c8 (claude              2025-12-02  140)         DiffSpec::TwoCommit(s, e) => {
fe2c4c8 (claude              2025-12-02  141)             let from = resolve(repo, &s)?;

Install

Mac, Linux, Windows (WSL)

curl -sSL https://usegitai.com/install.sh | bash

Windows

powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://usegitai.com/install.ps1 | iex"

No per-repo setup or git hooks required. Commit with the Agent, git, or your favorite git client. Attribution will be linked to commits automatically.

The Git AI standard is supported by:

				+ Add an Agent

Our Choices

• 🪄 Transparent — Git AI requires no workflow changes. Just prompt and commit as you normally would and Git AI automatically attaches attribution metadata to every commit.
• ⚡ No performance overhead — Git AI does not rely on Git Hooks (slow + difficult to set up in every repo) and it does not wrap the Git binary. Your Git operations are just as fast as they were before Git AI was installed.
• 💻 Local-first — Works offline, no login required.
• 🔒 Secure Prompt Storage — Git AI links each line of AI-code back to the prompt that generated it. These sessions are scanned and redacted, and saved outside of Git -- keeping repos lean, enabling fine-grained access control, and preventing PII or secrets from leaking.
• 🌐 Git native and open standard — Git AI built the open standard for tracking AI-generated code with Git Notes.

Documentation

• CI Actions preserves attribution through Rebase and Merge & Square and Merge.
• How Git AI Works
• Stats command - aggregate % AI stats across commits
• AI Blame -
• Config -
• Add support for an agent in Git AI
• Install Git AI in Background Agents: Claude Web, Codex Cloud, Cursor Agent, and Devin.

Attribution Stats

Line-level AI-attribution let you track AI-code through the full SDLC. Track how much AI code gets accepted, committed, through code review, and into production — to identify which tools and practices work best.

git ai stats --json
git ai stats <start_sha>..<end_sha> --json

Calculates % AI-code, AI-lines generated vs committed, accepted rates, human overrides broken down by tool and model. Learn more: Stats command reference docs.

{
  "human_additions": 28,
  "ai_additions": 76,
  "ai_accepted": 47,
  "git_diff_deleted_lines": 34,
  "git_diff_added_lines": 104,
  "tool_model_breakdown": {
    "claude_code/claude-sonnet-4-5-20250929": {
      "ai_additions": 76,
      "ai_accepted": 47
    }
  }
}

AI Blame

Git AI blame is a drop-in replacement for git blame that shows AI attribution for each line. It supports all standard git blame flags.

git ai blame /src/log_fmt/authorship_log.rs

cb832b7 (Aidan Cunniffe 2025-12-13 08:16:29 -0500  136)     format: DiffFormat,
cb832b7 (Aidan Cunniffe 2025-12-13 08:16:29 -0500  137) ) -> Result {
fe2c4c8 (claude         2025-12-02 19:25:13 -0500  138)     // Resolve commits to get from/to SHAs
fe2c4c8 (claude         2025-12-02 19:25:13 -0500  139)     let (from_commit, to_commit) = match spec {
fe2c4c8 (claude         2025-12-02 19:25:13 -0500  140)         DiffSpec::TwoCommit(start, end) => {

There are community plugins that display AI-attribution in popular IDEs, color-coded by agent session. Hover over a line to see the raw prompt or summary.

Supported Editors

• VS Code
• Cursor
• Windsurf
• Antigravity
• Emacs magit
• Built support for another editor? Open a PR

For teams and enterprises

We built Git AI for Teams to make it easy to roll out Git AI across your organization. Just connect GitHub, GitLab, Bitbucket, or Azure DevOps and get aggregate insights across all your repositories, plus the full trace of every agent session—from prompt all the way to production.

• See how much AI-code makes it all the way to production
• Measure % AI and token cost by Pull Request, Repo, Team, and Contributor
• Measure and improve agent autonomy and token efficiency
• Measure AI-code durability and how much rework AI-code requires before and after deployment
• Tie incidents back to AI-sessions
• Save prompts behind every generated hunk of code for harness engineering and code review

FAQs

How does it work?

1. Coding Agents call git-ai checkpoint whenever they write code or modify files with bash scripts. 1. On commit, Git AI stores line-level attribution data in Git Notes, linking each line of AI-generated code to the agent, model, and session that created it. Run git log --show-notes="ai" to see them. 1. Git AI moves and merges line-level attributions when you squash, merge, reset, rebase, stash, cherry-pick, etc. so your AI code is always accurately tracked.

Git AI does not use AI or heuristics to "detect" AI code — the Agents report exactly which lines they wrote, providing the most accurate, explicit attribution possible.

Does the agent have to commit for Git AI to attribute the code?

Git AI notes are attached to commits — how are attributions preserved when I rebase, squash, stash, cherry-pick, etc.?

Can I use this on my own?

Is there a performance impact?

Do I have to set up agent hooks?

Who uses this?

What's the difference between the open source CLI and the teams version?

Who built this?

What are the capabilities and known limitations?

Here is a full breakdown of what is supported today:

| Capability | Status | Notes | | --------------------------------------------------------------- | ------ | ---------------------------------------------------------------------------- | | Edit / Write / Patch tools | ✅ | Line-level attribution recorded automatically. | | Files created via Bash | ✅ | May not work if the agent is not operating from the repository root. | | Git worktrees | ✅ | Attribution maintained across linked worktrees. | | Background Agents | ✅ | See docs for Claude Web, Codex Cloud, Cursor Agent, and Devin. | | Attribute lines from multiple Agent Sessions in the same commit | ✅ | | | Record which lines a human overrode | ✅ | | | Attribute sessions that produced no code | ✅ | Records token usage and session activity even when no code is accepted. | | Accepted rate per session | ✅ | | | Added and deleted lines per session | ✅ | | | Tool-call level attribution | ✅ | Resolves attributed lines to the tool call that generated them. | | Tokens and cost per commit and PR | ✅ | Aggregates token usage and cost across the sessions behind each commit/PR. | | Formatters | ✅ | Formatting will not change attribution to human. | | Multi-repo root | ⚠️ | If you run an agent that edits multiple repos, Bash attributions only work when the agent runs each command with its cwd inside that repo. |

Git Rewrite Operations:

| Operation | Status | Notes | | --------------------------------------------------------------- | ------ | ---------------------------------------------------------------------------- | | git rebase | ✅ | Attribution preserved. View Code | | git cherry-pick | ✅ | Attribution preserved. View Code | | git stash / git stash pop | ✅ | Attribution preserved. View Code | | git merge --squash | ✅ | Attribution preserved. View Code | | git reset --soft | ✅ | Attribution preserved. View Code | | git reset --mixed | ✅ | Attribution preserved. View Code | | git reset --hard | ✅ | Attribution preserved for commits that remain in history. View Code | | git merge (merge commit) | ✅ | Attribution preserved. View Code | | git commit --amend | ✅ | Attribution preserved, including unstaged and partially staged changes. View Code | | git checkout / git switch (branches) | ✅ | Attribution follows the working tree across branch changes. View Code | | git pull (fast-forward / --rebase) | ✅ | Attribution preserved, including autostashed changes. View Code | | git push / git fetch | ✅ | Attribution notes synced to/from the remote. View Code | | git mv | ❌ | Renames are not yet tracked; attribution does not follow the moved file. | | git filter-branch / git filter-repo | ❌ | Bulk history rewrites are not tracked. | | git replace | ❌ | Object replacements are not tracked. |

GitHub, GitLab, Bitbucket, Azure DevOps:

| Capability | Status | Notes | | --------------------------------------------------------------- | ------ | ---------------------------------------------------------------------------- | | Squash and Merge | ✅ | Requires Git AI for Teams or Open Source CI Actions to preserve attribution. | | Rebase and Merge | ✅ | Requires Git AI for Teams or Open Source CI Actions to preserve attribution. |

License