Option to suppress/collapse file edit diffs in terminal output

[clintoncodewell]

Feature Request

Add a configuration option to suppress or collapse code change / content diff output shown in the terminal after file edits.

Problem

When Claude Code edits files, the full diff is displayed in the terminal. For large or frequent edits, this creates a lot of visual noise and makes it harder to follow the conversational flow. There's currently no way to hide or minimize these diffs.

Proposed Solution

A setting (e.g., showDiffs: false or diffVerbosity: "collapsed") that controls whether file edit diffs are shown inline in the terminal output. Options could include:

• full (default, current behavior) — show the complete diff
• collapsed — show a one-line summary (e.g., "Edited src/foo.ts — 12 lines changed") that can be expanded
• none — suppress diff output entirely

This could be configured via:

• settings.json ("diffDisplay": "collapsed")
• CLI flag (--diff-display=none)
• Or both

Use Case

• Users working on large refactors or multi-file changes where diffs dominate the output
• Scripted/automated workflows where diff output is unnecessary
• Users who trust Claude's edits and prefer a cleaner conversational flow, reviewing changes via git diff instead

🤖 Generated with Claude Code

[github-actions]

Found 3 possible duplicate issues:

1. Option to hide inline diffs for Edit/Write tool output #37951
2. Option to collapse file edit diffs by default (expand on demand) #37584
3. Feature request: option to hide/minimize diff output for Edit tool #30139

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #37951.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.