We built git blame for AI agents - here's how it works

Your team uses Claude Code, Cursor, or Gemini to write code. 60-80% of new commits are AI-generated. But when a bug appears - can you answer: which AI wrote this line? We built Origin to solve this. Here's how it works under the hood. The problem Traditional git blame shows who committed code. But when your whole team uses AI agents, "who committed" is always the developer — even when Claude wrote 90% of the file. You lose: • which agent generated the code • what prompt produced it • what model was used • what it cost How Origin tracks it Every time an AI agent starts a session, Origin hooks fire: # Claude Code hooks (auto-installed via origin init) origin hooks claude-code session-start origin hooks claude-code user-prompt-submit origin hooks claude-code stop When a commit happens, Origin writes session data to git notes: git notes show HEAD # Origin-Session: abc123 # Agent: claude-code # Model: claude-opus-4-6 # Cost: $2 .40 # Prompts: 12 AI Blame Now you can see who wrote every line