DevToolsAIVersion ControlProductivity

Agent Session Archaeology Plugin

Link Git blame with coding agent history to explain why each line exists

Problem
Code is increasingly generated by AI agents. Git blame shows the commit and author, but the original request and reasoning behind each line are lost in closed sessions. When developers need to understand or modify AI-generated code, they lack context and can only guess.
Solution
Locally saves coding agent sessions and uses git blame to automatically associate files, lines, or commits with the corresponding agent session, showing the original request and rationale. It also finds user edits after the session, forming a traceable chain of code intent.
Users
Developers using coding agents like Claude Code or Codex, especially those maintaining AI-generated codebases
MVP
Local session storage and indexing; git blame integration to locate lines; display associated original request and reasoning summary; search historical sessions; one-click jump to the corresponding commit
Revenue
Free basic version + subscription pro (team-shared session library, cross-project search, export reports)
Why now
Coding agents are rapidly spreading, but tooling still dates from the traditional git era, lacking tracking of AI-generated code intent—an indie developer can fill this workflow gap

Source discussions · 1

  1. Hacker NewsShow HN: KeepPlain – ask your coding agent why a line of code exists1↑ 0
← Back to list