pi: git-ai: trace code commits back to agent sessions

Git AI version 1.7.2 records AI agent checkpoints in Git notes, enabling developers to trace code commits back to specific agent sessions without altering commit messages or repository files. The tool, integrated with Pi via an extension, captures session IDs, model names, and touched files, as demonstrated by Thiago Perrotta, who shows `git ai blame` output attributing a line to a Pi session with model gpt-5.6-sol.

♠ Git AI https://github.com/git-ai-project/git-ai records agent checkpoints in Git notes https://git-scm.com/docs/git-notes <sup 1 https://perrotta.dev/2026/09/pi-git-ai-trace-code-commits-back-to-agent-sessions/ fn:1 </sup , without changing commit messages or repository files. In order to integrate it with Pi https://pi.dev/ we use an extension, because Git AI must observe file and Bash tool calls: js const GIT AI BIN = join homedir , '.git-ai', 'bin', 'git-ai' ; const child = spawn GIT AI BIN, 'checkpoint', 'pi', '--hook-input', 'stdin' , { stdio: 'pipe', 'ignore', 'ignore' , } ; The extension listens before and after each mutating call. It sends Pi session ID, model, tool, working directory, and touched files to git-ai checkpoint . In a shell script in my dotfiles, I configured git-ai : Git AI daemon receives Git Trace2 events through per-user socket. if command -v git-ai /dev/null 2 &1; then export GIT TRACE2 EVENT="af unix:stream:${GIT AI DAEMON TRACE SOCKET:-$HOME/.git-ai/internal/daemon/trace2.sock}" export GIT TRACE2 EVENT NESTING=0 fi After restarting Pi, code attribution starts to appear alongside normal git blame calls<sup 2 https://perrotta.dev/2026/09/pi-git-ai-trace-code-commits-back-to-agent-sessions/ fn:2 </sup : % git ai blame src/main.rs 442dfde2 pi 2026-09-05 14:29:59 +0200 1 fn main { println "pi" ; } The commit note contains the useful attribution / provenance snippet: "sessions": { "s 82565459b433c5": { "agent id": { "tool": "pi", "id": "pi-extension-test", "model": "gpt-5.6-sol" } } } Now a suspicious line can lead from Git history to the exact Pi session. The session ID can then subsequently be searched with fr https://perrotta.dev/2026/09/agentsview-vs-fast-resume/ or resumed in Pi. Other useful commands with real examples: % git ai show HEAD STYLE.md s f2908643b7ce0d::t 739223c8b9befd 12,29,48 --- { "schema version": "authorship/3.0.0", "git ai version": "1.7.2", "base commit sha": "d225f5e635bbf5494574591580af8abf93da9480", "prompts": {}, "sessions": { "s f2908643b7ce0d": { "agent id": { "tool": "pi", "id": "01a07acd-e9c7-759f-84b4-107f9ebc2556", "model": "gpt-5.6-sol" }, "human author": "Thiago Perrotta <{redacted email} " } } } % git log --show-notes=ai commit d225f5e635bbf5494574591580af8abf93da9480 HEAD - master Author: Thiago Perrotta <{redacted email} Date: Mon Sep 7 09:40:01 2026 +0200 docs: require problem statement questions Notes ai : STYLE.md s f2908643b7ce0d::t 739223c8b9befd 12,29,48 --- { "schema version": "authorship/3.0.0", "git ai version": "1.7.2", "base commit sha": "d225f5e635bbf5494574591580af8abf93da9480", "prompts": {}, "sessions": { "s f2908643b7ce0d": { "agent id": { "tool": "pi", "id": "01a07acd-e9c7-759f-84b4-107f9ebc2556", "model": "gpt-5.6-sol" }, "human author": "Thiago Perrotta <{redacted email} " } } } ∎ — § — Reply via email <mailto:serendipity@perrotta.dev?subject=Reply to: pi: git-ai: trace code commits back to agent sessions