git-ai

Compatibility and Limitations

Supported Agents

AgentAuthorshipPrompts
Cursor >1.7
Claude Code
GitHub Copilot in VSCode via Extension

Capabilities

CategoryFeatureStatus
Agent ModeAttribute LOC added with Write | Edit | MultiEdit tools (default)
Tab CompletionAttribute LOC from tab completions
EditingHuman edits of AI LOC move attribution to that developer
EditingAI edits of human LOC move attribution to the AI
EditingAdding code before or after AI Hunks does not break attribution (line shifting works)
EditingUndo / Redo operations correctly preserve attribution
EditingRestoring to a local checkpoint in your IDE restores that file's attribution to its old state
EditingCopy / Pasting AI LOC keeps them attributed to AI
EditingCode Formatting tools do not break attribution

Supported Git Workflows

Local

Git OperationStatus
Merging branches correctly merges attribution
Merging branches with --squash correctly merges attribution
reset --hard resets attribution to the base commit
git replace maintains correct attribution
git worktrees maintains correct attribution
Amending commits correctly preserves attribution
After resolving git conflicts, attribution is correct
Rebase correctly merges attribution
reset --soft and --mixed maintains correct attribution
Cherrypick correctly merges attribution
mv (move or rename files) moves AI attribution to the new file
Stash / Pop maintain correct attribution

Server-Side

Because Authorship Logs are linked to commit hashes, server-side operations that create new commits will not have logs attached. You'll have to manually run git-ai squash-authorship after the squash or merge operation to update the attribution.

We'll be publishing CI scripts and Apps to assist with this soon.

PlatformOperationStatus
GitHubRebase / Merge⚠️ Requires GitHub Action or Webhook
GitHubSquash and Merge⚠️ Requires GitHub Action or Webhook
GitLabSquash and Merge⚠️ Requires CI Runner or Webhook
BitBucket CloudSquash and Merge⚠️ Requires CI Runner or Webhook