[FEATURE] Add setting to control Edit tool output verbosity

Resolved 💬 3 comments Opened Dec 4, 2025 by jupediaz Closed Dec 8, 2025

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

After each Edit tool call, Claude Code displays detailed cat -n snippets showing the exact file modifications. This causes:

  1. Conversations become extremely long during refactoring sessions
  2. Extra tokens consumed displaying diffs the user doesn't need to see
  3. Difficult to navigate chat history when making many edits
  4. No way to disable or minimize this output currently

Proposed Solution

Add an editOutputVerbosity setting in .claude/settings.json with options:

  • full - Current behavior (show complete diff snippet)
  • minimal - Only show "File X updated successfully"
  • none - Silent, no output

Example config:
{
"editOutputVerbosity": "minimal"
}

Alternative Solutions

Currently there's no workaround. Users must scroll through long conversations filled with repetitive diff outputs.

Similar functionality exists for bash with BASH_MAX_OUTPUT_LENGTH, so extending this pattern to Edit tool output would be consistent.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

  1. I'm refactoring a Next.js app to use centralized i18n dictionaries
  2. This involves 50+ Edit calls across 10+ files
  3. Each edit shows a 10-20 line diff snippet I don't need to verify
  4. The conversation becomes 3x longer than necessary
  5. With editOutputVerbosity: minimal, I'd just see "File updated" and continue working efficiently

Additional Context

This would significantly improve UX for power users who trust the tool and don't need to verify every character change. The detailed output could remain as default for new users who want visibility.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗