The diff is a summary. The session trace is what actually happened.
Summary
An article highlighting that AI agent session traces reveal hidden actions (e.g., undeclared keys, scope creep) that are absent from the final PR diff, and warns that most developers review only the diff, not the full trace, leading to unreviewed risks.
Similar Articles
Few: two instances of the same model don't make the same diff
An observation that two instances of the same AI model on the same task can produce different internal behavior (e.g., one refactoring a shared utility while the other does not), highlighting the challenge of reviewing agent work by final output alone.
AI coding agent output verification in 2026: read the diff, vibe check it, merge
A reflection on current practices for verifying AI coding agent output, noting that developers often skim diffs and merge without fully auditing the agent's session activity, raising concerns about code review culture in the age of AI.
Use AI for reviewing code especially when the diff is huge
The article argues that human code reviewers should use AI to handle large diffs, and instead contribute their out-of-distribution knowledge and high-level context.
I'm tired of manually debugging traces
A developer builds a debugging tool for AI agents that compares replays against reference runs to identify where behavior first drifted, expressing frustration with manual trace debugging.
Show HN: Codiff, a local diff review tool
Codiff is a minimal, local diff viewer for reviewing staged and unstaged Git changes, with LLM-powered walkthroughs and inline review comments.