Omniscio

OmniscioGuidesClaude Code diff panel

Claude Code diff panel: what /diff shows, what it needs, and why it can look empty

In fullscreen rendering, /diff opens a panel beside the conversation instead of a viewer you have to close. It lists the files Claude has changed, with added and removed line counts, and draws each file's diff under the list.

It refreshes every time Claude edits a file or runs a shell command. This page covers the three steps that open it, the five things you can do inside it, the reasons it can show nothing, and the two keys worth learning.

Sources read November 8, 2026. By the Omniscio team. Updated .

Find the situation you are in

If your question is about restoring a file to an earlier point rather than reading what changed, the checkpoints guide is the right page, because /diff only shows.

What /diff opens

The command has one job in both renderers: it lets you look over the changes in your working tree without leaving Claude Code.

You see the edits Claude has made so far alongside anything else you have not committed. That is wider than "what Claude did this turn", and it is the first thing to hold on to when a file you expected is missing.

What opens depends on the renderer.

  • Fullscreen rendering: the diff panel opens beside the conversation, stays open, and updates while you keep working.
  • The classic renderer: the diff dialog opens above the prompt, and you close it when you are done reading.

The panel arrived in v2.1.260. Anthropic's release note for that week describes it as replacing a viewer you had to close.

Both surfaces come from the same place: cc-plugin-diff, one of the mods built into Claude Code. That is worth knowing for one practical reason.

Disable that mod in /plugin and /diff opens Claude Code's earlier panel and diff viewer instead. A guide written before v2.1.260 is then describing a surface you can still reach deliberately. What a mod is, and which switch stops one, belongs to the mods guide.

Two boundaries shape the list before you read a single line of it.

  • A submodule is one entry. It appears only when the commit it points to changes, so edits to files inside it do not appear.
  • The per-turn views come from Claude's own file edits, not from git. A change Claude made by running a shell command appears only under Current, the working-tree view.

The dialog, when you are not in fullscreen

Outside fullscreen rendering, /diff opens the diff dialog as a bordered block above the prompt. It lists your changed files with their added and removed line counts, and compares them against HEAD or against whatever you last chose in the diff panel for that repository. That is why the two surfaces can disagree about the same tree.

Once Claude has edited files, a source picker appears above the list, with one turn view per prompt that led Claude to edit files. Current returns you to the working tree.

The keys are plain:

  • Up and Down select a file, and Enter opens the selected file's diff.
  • Esc returns from a diff to the list, or closes the dialog from the list.
  • Tab moves to the source picker. In a file's diff, it moves to the ask button, and Enter attaches that file's diff to your next prompt.

The choice between the two surfaces is the tui setting, not a setting of the panel's own: /tui fullscreen and /tui default are the switch.

If you are staying in the classic renderer, the panel's requirements do not apply to you at all, and the 110-column minimum is only about the panel.

Open it

Needs Claude Code v2.1.287 or later, and then three steps:

  1. Switch to fullscreen rendering with /tui fullscreen. /tui on its own prints which renderer is active.
  2. Make the terminal at least 110 columns wide.
  3. Run /diff inside a git repository.

If it still does not appear

If it still does not appear, the width is the usual reason.

The installed build carries the string Resize your terminal to at least 110 columns to show the diff panel. It was found by a text search of the build on the day this page was written, rather than read off a screen. That is the sentence to look for.

A wide conversation that gains a right-hand column which disappears as you drag the window smaller is the width problem above, and that is the string to look for.

The panel first arrived in v2.1.260, and the requirement today is a later release than the one that introduced it. A build from the launch week can therefore behave differently from the one the current reference page describes.

Which version you need

This page was written against Claude Code v2.1.319. Run claude --version to check what you have, because /diff changed in several releases after it launched.

Two more things about fullscreen rendering, since it is the part people are missing.

  • It is a research preview, and it works at any window size. A maximized window is not what the panel wants: columns are.
  • Claude Code refuses the switch in a session holding a restriction it cannot pass to the restarted process. It prints Cannot switch renderers in this session with the reasons instead of switching, which looks at first like the command did nothing.

Reading a change in the panel

The list is a file list with a diff under it. Each row carries the file's added and removed line counts, and the selected row's diff is drawn below the list.

The refresh is the part that separates it from a viewer. Claude Code refreshes the panel each time Claude edits a file or runs a shell command. It is meant to be watched while a turn runs, rather than opened afterwards.

Five things are available while it is open:

  • Jump to a file and scroll its diff.
  • Ask Claude about a file's changes, which attaches that file's diff to your next prompt.
  • Show one turn's edits with the source picker.
  • Expand the files the list leaves out.
  • Change what the panel compares against.

The first and the fourth are the ones that decide whether a file is on screen at all.

Click a row to jump to it, and scroll the panel with the mouse wheel. When the file list itself overflows, scroll the list with Ctrl+Up and Ctrl+Down, or Meta+Up and Meta+Down, where Meta is Alt on Windows and Linux and Option on a Mac.

Two count lines sit at the bottom of the list: one for the test and generated files it skipped, and one for the changes it collapsed from before this session. Click either line to expand it, which is how a wall of test fixtures stays out of the way until you ask for it.

The second and third do more than display.

Click ask, at the right of the file's name above its diff, and Claude Code attaches that file's diff to your next prompt. The button reads asked ✓ until you send that prompt, and asking on a second file replaces the first.

Click the source picker in the header to choose one turn's edits. Turns are labelled T1, T2 and so on, and Current returns you to the working tree.

The fifth decides what the diff is measured against. Ctrl+X B cycles three bases: this session's changes, your uncommitted changes as one list, and everything since your branch split from the default branch. Claude Code remembers the choice for each repository, which is convenient until it is the reason a change looks missing.

What you cannot do from the panel is accept or reject a change.

That list above is the whole of what Anthropic offers, and accepting or discarding belongs to your own review, in git or in the editor. Omniscio's own viewer, further down, is the surface that does offer it.

One open request, issue 98002, asks for a setting to dock the panel on the left instead of the right.

When it shows nothing, or the wrong thing

If the panel is empty, check these first:

  • Is the session inside a git repository? Outside one the panel has nothing to read.
  • Expand the two count lines at the bottom of the list, for skipped test and generated files and for changes collapsed from before this session.
  • Press Ctrl+X B, in case the base is this session rather than your working tree.

If the counts look right and every file's body reads No diff content, that is the message people search for, and one report explains it.

Issue 93073, open since 2026-09-09, says that with diff.mnemonicPrefix set in git config the file list and its line counts are right. Every tracked file's body, though, reads No diff content. The reporter traces it to a parser expecting the a/ and b/ prefixes that git then does not emit.

That is a report, not documented behaviour, and no release note we read fixes it.

Files created during the session are a second reported gap. Issue 99136 asks Anthropic to show them in the panel. The reporter's reason is that a file has to be staged before it can be read there. A brand new file can therefore be missing from the list until it is.

Two failures do have documented fixes.

The message Diff unavailable appeared in a repository with a file or folder named HEAD at its top level. A pane could also open blank in sessions where 64 or more turns edited files. v2.1.319 fixes both.

A slow refresh on a very large repository is not a hang either. v2.1.316 changed the panel to run one fewer full-repository git command per refresh, and to space refreshes out when git is slow.

One case looks like a bug and is deliberate. During an unfinished merge, rebase, cherry-pick or revert, the panel keeps showing the changes it last read from git, so the operation's incoming changes do not flood the list. It updates at its first refresh after the operation ends, for example when Claude next edits a file.

Changing the keys

Two actions are worth knowing by name. The built-in cc-plugin-diff mod draws the panel and handles all three.

  • app:cycleDiffBase is the Ctrl+X B base cycle. It sits in the DiffPanel context, which is active while the panel is open.
  • app:diffFileListUp and app:diffFileListDown scroll an overflowing file list. They default to Ctrl+Up and Ctrl+Down, or Meta+Up and Meta+Down, where Meta is Alt on Windows and Linux and Option on a Mac.

Three more actions can confuse a search.

app:toggleReplTab is described as opening or closing the panel, but it has no default binding. It, app:toggleDiffNoiseFilter and app:toggleDiffPreSession reach only the earlier panel that /diff opens after cc-plugin-diff is disabled. Binding one of them and expecting the new panel to answer is a dead end worth knowing about.

The file is ~/.claude/keybindings.json, and changes are applied without restarting Claude Code. This example moves the base cycle off its chord and unbinds the default:

{
  "$schema": "https://www.schemastore.org/claude-code-keybindings.json",
  "bindings": [
    {
      "context": "DiffPanel",
      "bindings": {
        "ctrl+x b": null,
        "f2": "app:cycleDiffBase"
      }
    }
  ]
}

Setting an action to null unbinds it, which is the only way to free a chord. The chord in question here needs Claude Code v2.1.260 or later to exist at all. The keybindings file, its contexts and its validation rules are the keyboard shortcuts guide's subject rather than this page's.

When it opens on its own, and how to keep it closed

The panel has two ways of arriving unasked, and both are documented.

  • It opens on its own once Claude starts editing files if your terminal is at least 144 columns wide.
  • Separately, once you have opened it yourself with /diff, later sessions open it as soon as Claude edits a file in any terminal wide enough to fit it.

In both cases, closing it keeps it closed, in this session and in later ones, until you run /diff again.

To close it, run /diff again or click the ✕ in the panel's header.

If a wide terminal opened the pane when it had nothing to show, that specific case was fixed in v2.1.311. An older build is worth ruling out before you conclude the behaviour is random.

Three reports describe the panel arriving or staying when it was not wanted, and they are not the same shape. Each is a report rather than a documented rule.

  • Issue 93160, open since 2026-09-09, reports the panel opening on its own whenever there are uncommitted changes. That report does not say how wide its terminal was, and the rule above is the 144-column case, so it stands as an open question rather than a second rule.
  • Issue 97935, on 2.1.283, says the ✕ did not close it.
  • Issue 103754, on 2.1.304 in Warp on macOS, is different again: that reporter did not know how to close the panel, which is the discoverability gap the two documented ways are meant to answer.

Where this page stops

This page owns the panel and the dialog. What a mod is belongs to the mods guide, the keybindings file to the keyboard shortcuts guide, and restoring files rather than reading them to the checkpoints guide. Everything else about a session is indexed in the other Claude Code guides.

Omniscio's own diff viewer

Omniscio is the desktop app we make for running many Claude Code sessions at once, and its own diff viewer does what the panel does not: it reviews changes.

A rejection discards, so read these keys twice.

  • J and K move between files.
  • Y and X accept or reject the selected file, and Shift+Y and Shift+X do it for all of them.
  • An N of M reviewed count sits beside Accept all and Reject all.

The Review changes library page covers the rest, and the features page and download page cover the app itself.

Sources

Every behaviour on this page rests on one of these, and each was read on the date beside it.

  • Interactive mode, for the /diff section, the panel and dialog sections, the requirements list, the auto-open widths, and every control quoted here. Read November 8, 2026.
  • Keybindings, for the diff panel actions, their defaults and contexts, the file format and the version note on the ctrl+x b chord. Read November 8, 2026.
  • Fullscreen rendering, for /tui, the research preview status, and the refusal to switch renderers. Read November 8, 2026.
  • Week 36 release notes, for how the panel was announced beside v2.1.260. Read November 8, 2026.
  • Changelog at v2.1.260, for the release that added the panel. Read November 8, 2026.
  • Changelog at v2.1.319, for every later change to /diff: the v2.1.311 fix, the v2.1.316 large-repository work and the two v2.1.319 fixes. Read November 8, 2026.
  • The six issue pages linked above, each read on November 8, 2026, with its state, reaction count and comment count taken from the issue itself.
  • Omniscio's own Review changes library page, read on November 8, 2026, and the source files the fact ledger names for its keys and its summary line.
  • Two captures on this machine on November 8, 2026: claude --version, which printed 2.1.319 (Claude Code), and a text search of that build for the narrow-terminal string and the mod id.

Two of these move often: the interactive mode page and the changelog. If a release note mentions /diff, read both again before trusting a copy of this page from a few weeks back.

Common questions

Does Claude Code have a diff panel?

Yes. In fullscreen rendering, /diff opens a diff panel beside the conversation instead of a viewer you have to close, and it refreshes each time Claude edits a file or runs a shell command. It needs Claude Code v2.1.287 or later, fullscreen rendering, a git repository, and a terminal at least 110 columns wide. Outside fullscreen rendering /diff opens the older diff dialog above the prompt instead.

Why does the Claude Code diff panel show no diff content?

Check three things first. The list skips test files and generated files, and collapses changes from before this session, so expand the count lines at the bottom of the list. The comparison base may be this session rather than your working tree, so press Ctrl+X B until the header reads the base you want. The panel also needs a git repository, so a session outside one has nothing to read. If the counts are right and every body still reads No diff content, an open report names diff.mnemonicPrefix in git config as the cause.

How do I close the Claude Code diff panel?

Run /diff again, or click the ✕ in the panel's header. Closing it once keeps it closed in that session and in later sessions, until you run /diff again. If neither works, one open report on v2.1.283 says the ✕ did not dismiss it, and a second on v2.1.304 in Warp describes not finding the way out at all, so you are in a reported case rather than a documented one.

Why did the Claude Code diff panel open by itself?

That is documented behaviour at a wide width: the panel opens on its own once Claude starts editing files if your terminal is at least 144 columns wide. There is a second case. Once you have opened it yourself with /diff, later sessions open it as soon as Claude edits a file in any terminal wide enough to fit it. Close the panel and it stays closed until you run /diff again. v2.1.311 fixed a related case, where a wide terminal opened the pane when it had nothing to show.