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
I published a cli that Claude can use to record the rationale behind its changes called diff-rationale
The author shares 'diff-rationale', a CLI that records the reasoning behind file changes via git, allowing AI agents like Claude to preserve rationale across sessions and query it later.
Show HN: RealDiff – runtime behavior diffing for pull requests (six languages)
RealDiff is an open-source tool that detects runtime behavior changes in pull requests by comparing test outputs, highlighting unintended effects even in files not directly edited.
Diffsmith
Diffsmith is a tool that lets you comment on your AI agent's code and collaborate on changes.
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.