CLI should offer IDE extensions to automatically light up diffs when used in an IDE terminal pane

[RyanHecht]

[DovieW]

wouldn't you just use the actual Github Copilot at that point?

[RyanHecht]

wouldn't you just use the actual Github Copilot at that point?

A fair point, @DovieW, you could certainly just use the existing native Copilot extensions for your IDE of choice! During internal and private previews, though, we heard from users that they would like the option of using the CLI as their main interface with Copilot and simply using the IDE/editor as a visual way to view diffs prior to accepting changes.

We want to enable as many different ways of collaborating with Copilot as possible!

[DovieW]

I'll just spit ball an idea. The diff data can be stored in the workspace folder (could be a submodule in the .git folder) and then VS Code can always pick up that there are AI edits to be approved. This would allow using a none VS Code terminal while still having a GUI for diffs...

[SteveMinhDo]

wouldn't you just use the actual Github Copilot at that point?

i donot like to use vscode extension and I'd like everything in cli. Why do I need 2 panes for cli and vscode extension when working with vscode IDE as a developer.

Because of this integration issue, I have decided to use claude code instead.

[examon]

This should be resolved as of v0.0.409. The CLI now integrates with VS Code -- when connected via /ide, file-edit diffs are automatically opened in the IDE for visual review. The ide.open_diff_on_edit setting controls this behavior and is enabled by default. If you believe this isn't resolved, feel free to reopen this issue.