Overview
How might we design smart diff so people can trust and act on AI output?
When to use
- Perfect for collaborative editing tools, version control systems, and document platforms where intelligent change visualization improves review and collaboration.
When to skip
- Brand-new blank generations with no prior document to compare.
- Tiny single-field edits where a full diff pane is heavier than undo.
- Streaming chat replies that are not meant to mutate an existing artifact.
Rules
Applying AI edits with no visual diff and only a buried undo.
Raw line diffs that ignore semantic groupings users care about.
Accept-all with no way to accept hunks selectively.
Diffs that hide deletions or move them off-screen.
Evidence
| Product | Implementation |
|---|---|
| GitHub | Pull request diffs and Copilot suggested-change review. |
| Google Docs | Suggesting mode that marks AI or collaborator edits for review. |
| Notion | AI rewrite previews that show before/after on selected blocks. |
| Cursor | Inline and multi-file diffs for agent and composer edits. |