[FEATURE] GitHub change list panel for staged/uncommitted work

Resolved 💬 1 comment Opened May 8, 2026 by erockr Closed Jun 6, 2026

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

What I want

A Claude Code UI panel that shows the current repo's pending changes —
staged, unstaged, and untracked — similar to JetBrains' "Local Changes"
or VS Code's Source Control panel. Ideally with:

  • A flat list of changed files with status (M / A / D / ?? / staged-vs-not).
  • Click a file to see its diff inline.
  • Tie-in to the current branch / upstream so I can see "ahead by N commits"

and what they touch.

Why

Right now when Claude makes edits across several files in a session, the
only way I get a structured view of what's about to be committed is to ask
Claude to echo the file list, or run git status / git diff --stat
myself. A persistent panel would be faster and would also help me spot
files Claude touched that I didn't expect, before they ship.

Where it'd live

Wherever the chat / tool-trace panel currently lives — it's the same
surface area I'm already looking at. Probably a tab alongside chat history,
or a collapsible sidebar.

Workaround today

Asking Claude to run git status and git diff --stat and echo the
file names back. Works, but it's a manual prompt every time and the
result scrolls away in chat.

Proposed Solution

What I want

A Claude Code UI panel that shows the current repo's pending changes —
staged, unstaged, and untracked — similar to JetBrains' "Local Changes"
or VS Code's Source Control panel. Ideally with:

  • A flat list of changed files with status (M / A / D / ?? / staged-vs-not).
  • Click a file to see its diff inline.
  • Tie-in to the current branch / upstream so I can see "ahead by N commits"

and what they touch.

Why

Right now when Claude makes edits across several files in a session, the
only way I get a structured view of what's about to be committed is to ask
Claude to echo the file list, or run git status / git diff --stat
myself. A persistent panel would be faster and would also help me spot
files Claude touched that I didn't expect, before they ship.

Where it'd live

Wherever the chat / tool-trace panel currently lives — it's the same
surface area I'm already looking at. Probably a tab alongside chat history,
or a collapsible sidebar.

Workaround today

Asking Claude to run git status and git diff --stat and echo the
file names back. Works, but it's a manual prompt every time and the
result scrolls away in chat.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

File operations

Use Case Example

I've edited a bunch of files I need to commit.
You added a bunch of Dev Tools screenshots I don't want committed.
I want to see all files that a commit would affect.

I'm used to seeing this in VS Code and find it reassuring but prefer Claude Code on the macOS Desktop.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗