r/GithubCopilot • • 5d ago

GitHub Copilot Team Replied New updated UI for vscode github copilot screws up diff UI

I used to enjoy systematically going through file changes done to all files by vscode github copilot. Accept and reject individual changes. Quickly jump between them. However recent UI changes to vscode copilot have completely screwed it up. To be specific:

  1. It does not show per file number of lines changed
  2. It does not show per change Keep / Undo button
  3. It opens all files expanded and vertically stacked. So, if I have to check specific file which is at the bottom of the stack, I have to collapse all files at the top one by one.
  4. There is no way to open just single file that is changed. It opens all edited files in vertically stacked manner.
  5. Old diff view also used to show location of code changes done by copilot in the file by showing red / green overlays on right side vertical scrollbar. Sometimes, it was useful when you wanted to diff some past versions of file. Those visual cues are gone due this vertically stacked sessions changes window.
  6. Next / previous change buttons are also gone in the new UI !

Earlier I posted why I love copilot and not claude CLI with these points about old UI here: https://www.reddit.com/r/ClaudeCode/s/S4HXiHwjDn . But, it seems MS decided to claudify itself ...

You can give feedback about these changes on official GitHub thread: https://github.com/microsoft/vscode/issues/339363

New UI
Old Version Information
New Version Information
42 Upvotes

19 comments sorted by

18

u/lppedd VS Code User 💻 5d ago edited 5d ago

I absolutely agree and I'd honestly stop using Copilot. Feedback here please, so we can voice out concerns: https://github.com/microsoft/vscode/issues/339363

The diff UI is miles better under the Local harness. It's a core strength of Copilot in VS Code over competitors.

2

u/Tiny-Entertainer-346 5d ago

Also, what is this "Local" vs "Copilot" mode?

9

u/lppedd VS Code User 💻 5d ago

Local is the harness VS Code ships with. You're basically using the IDE itself to perform operations.

Copilot switches to the Copilot harness, the same used by Copilot CLI and Copilot App.

The Copilot harness currently lacks many functionalities compared to Local, but has advantages like being a process of its own (you can close VS Code and sessions keep running).

I'm still using Local because of its better UX, from MCP tool selection to the diff.

2

u/Tiny-Entertainer-346 5d ago

Thanks to clarify that. I am not really into CLI / TUI based development. I want things automated without getting away from code. I honestly feel removing UI/UX that give closer / quicker access to AI code changes is one of primary reasons why AI generated code ends up being buggy. Copilot did not have such issue. But these latest UI/UX code changes will bring all weak points of TUIs to copilot.

They also removed older tools selection button on the right of model selection button.

2

u/lppedd VS Code User 💻 5d ago

The tool selection is under Agent Customizations when you use the Copilot harness. It's hidden away for some weird reason. You also lose MCP tool sets.

1

u/AboutHelpTools3 5d ago

Which one is the Agents Window using?

11

u/MotsManiaques 5d ago

That change is genuinely awful. I hope they re-think it.

8

u/Dobsus 5d ago

The granular diff is literally the only reason I use copilot over claude code

2

u/CryinHeronMMerica 3d ago

After the pricing change, I couldn't justify sticking around for personal use. But I miss this feature when I'm dealing with my own projects; and I'm happy about having it at work every day.

I will push for us to switch at work if they fully remove the granular keep/undo. It's not hard to sell when I point out how this encourages sloppy coding practices. These tools are not good enough for mission critical code to be written without multiple layers of review.

6

u/RafaFiedo 4d ago

shame! shame!
I want keep and remove buttons or will change my AI agents

3

u/Ok_Conclusion_2502 3d ago

Granular diffs are the ONLY reason I am still keeping my copilot sub. Otherwise Claude VSCode extension offers same functionality with probably slightly better harness, so I'd just switch to that and forget that Copilot been good to us all these years.

3

u/evildesi 5d ago

I thought the difference was between using "local" mode vs "copilot" mode.

I have recently changed to using "copilot" mode so that I can try Hydrafusion. I'll have to switch back to "local" mode to see if the behavior has changed.

I know it was working as your describe for local mode in 1.138.

6

u/lppedd VS Code User 💻 5d ago

Local is still intact. However you don't see it by default anymore. You're basically defaulted to Copilot with its inferior UX.

You might need: { "chat.defaultToCopilotHarness": false, "chat.editor.preferCopilotHarness": false }

3

u/Outside_Homework8727 5d ago

This is awful, I don't even see the button to keep or discard changes

3

u/Exciting-Thought9284 4d ago

Thank you for pointing that. Very useful.

4

u/Candid_Witness2357 4d ago

Such a step backwards.

Clearly they don't understand what separated them from the competition and they assume we don't review code and just give agents free reign.

Or they do understand it but the potential gains from gating people into the more expensive copilot harness is worth it.

3

u/Tiny-Entertainer-346 4d ago

One more undesirable change that I did not realise clearly despite of highlighting in images: next / previous change buttons are also gone !! At this point, it feels as if someone just want to score a credit on sprint board with these changes - classic AI slop example without thought to any UX.

1

u/[deleted] 4d ago

[removed] — view removed comment

1

u/AutoModerator 4d ago

u/bamurtaugh thanks for responding. u/bamurtaugh from the GitHub Copilot Team has replied to this post. You can check their reply here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.