claude-code - 💡(How to fix) Fix Feature: external diff viewer alongside CLI approvals [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48278Fetched 2026-04-16 07:04:19
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Feature request

Add a diffTool config that opens diffs in an external viewer (e.g. IntelliJ, opendiff) in addition to showing them in the CLI.

The diff should appear in both places simultaneously - CLI for approving/rejecting, external viewer for a richer visual read.

Why this matters:

  • For simple edits, users can approve straight from the CLI without switching screens.
  • For complex edits, the external viewer gives a better place to read the full diff without losing the CLI approval flow.

Current problem:

The JetBrains plugin takes over entirely - it moves both the diff display AND the approval flow into the IDE, forcing users to switch contexts for every edit regardless of complexity. There is no way to use the IDE as a read-only diff viewer while keeping the CLI as the primary approval interface.

Proposed behavior:

A config option (e.g. diffTool: "idea diff") that launches an external diff viewer when Claude proposes an edit, while still showing the diff inline in the CLI and keeping the approve/reject flow in the terminal.

extent analysis

TL;DR

Implement a diffTool config option to launch an external diff viewer alongside the CLI diff display.

Guidance

  • Introduce a new configuration option, e.g., diffTool, to specify the external diff viewer to use.
  • Modify the diff display logic to launch the external viewer in addition to showing the diff in the CLI.
  • Ensure the approval flow remains in the CLI, allowing users to approve or reject edits without leaving the terminal.
  • Consider adding support for multiple external diff viewers, such as IntelliJ and opendiff, to cater to different user preferences.

Example

// Example config option
const config = {
  diffTool: 'idea diff'
};

// Pseudo-code to launch external diff viewer
if (config.diffTool) {
  const diffViewer = getDiffViewer(config.diffTool);
  diffViewer.launch(diffContent);
}

Notes

The implementation details may vary depending on the specific requirements and technical constraints of the project. This guidance provides a general direction for addressing the feature request.

Recommendation

Apply workaround: Implement the proposed diffTool config option to provide users with the flexibility to use an external diff viewer alongside the CLI. This approach allows for a more seamless editing experience, especially for complex edits that require a richer visual representation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING