Track the AI Code in your repositories
git_ai_commit_blame_and_bot.mov
curl -sSL https://usegitai.com/install.sh | bashpowershell -NoProfile -ExecutionPolicy Bypass -Command "irm http://usegitai.com/install.ps1 | iex"🎊 That's it! No per-repo setup. Once installed Git AI will work OOTB with any of these Supported Agents:
Once installed, all your Coding Agents will call Git AI in the background and mark the code they generate AI-authored.
After you commit, git-ai adds a git note to track which lines were AI-authored and scores each commit:
Aggregate git-ai data at the PR, developer, Repository and Organization levels:
- AI authorship breakdown for every Pull Request
- Measure % of code that is AI generated through the entire SDLC
- Compare accepted-rate for code written by each Agent + Model.
- AI-Code Halflife (how durable is the AI code)
By default Git AI stores prompt data locally only. To include prompts in git notes (authorship logs), set prompt_storage to notes:
git-ai config set prompt_storage notesWhen using notes mode, you can exclude specific repositories from having prompt data included:
git-ai config set --add exclude_prompts_in_repositories https://github.com/private-org/*
git-ai config set --add exclude_prompts_in_repositories /path/to/private/repoor to exclude all repositories:
git-ai config set --add exclude_prompts_in_repositories "*"🤖 Track AI code in a Multi-Agent world. Because developers get to choose their tools, engineering teams need a vendor agnostic way to track AI impact in their repos.
🎯 Accurate attribution from Laptop → Pull Request → Merged. Claude Code, Cursor and Copilot cannot track code after generation—Git AI follows it through the entire workflow.
🔄 Support real-world git workflows by making sure AI-Authorship annotations survive a merge --squash, rebase, reset, cherry-pick etc.
🔗 Maintain link between prompts and code - there is valuable context and requirements in team prompts—preserve them alongside code.
🚀 Git-native + Fast - git-ai is built on git plumbing commands. Negligible impact even in large repos (<100ms). Tested in Chromium.
- How Git AI Works and its Limitations
▶️ Video 🗺️ Diagram - Git AI Commands
- Configuring Git AI for the enterprise
git-ai automatically sets up all supported agent hooks using the git-ai install-hooks command
| Agent/IDE | Authorship | Prompts |
|---|---|---|
| Cursor >1.7 | ✅ | ✅ |
| Claude Code | ✅ | ✅ |
| GitHub Copilot in VSCode via Extension | ✅ | ✅ |
| Google Gemini CLI | ✅ | ✅ |
| Continue CLI | ✅ | ✅ |
| OpenCode | ✅ | ✅ |
| Atlassian RovoDev CLI | ✅ | ✅ |
| AWS Kiro (in-progress) | 🔄 | 🔄 |
| Continue VS Code/IntelliJ (in-progress) | 🔄 | 🔄 |
| Windsurf | 🔄 | 🔄 |
| Augment Code | 🔄 | 🔄 |
| OpenAI Codex (waiting on openai/codex #2109) | ||
| Junie & Jetbrains IDEs | ||
| Ona | ||
| Sourcegraph Cody + Amp | ||
| Google Antigravity |
| your agent here | | |
Building a Coding Agent? Add support for Git AI by following this guide