github / github/copilot-cli

Regression: "Open in VS Code" moved from one-click session action to Changes-panel dropdown

Open
#4,624 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

Describe the bug

Previously, "Open in VS Code" was a single, directly-clickable button in the session action bar, right next to "Create PR". Now it requires: opening the Changes panel/tab, clicking a small icon button, then selecting "Visual Studio Code" from an "Open in..." dropdown (which also lists Windows Terminal, PowerShell, Visual Studio 2019/2022, etc.). There's no "customize toolbar" option to pin VS Code back as a direct one-click action.

Affected version

1.0.80 (Windows)

Steps to reproduce
  1. Open a project session with uncommitted changes.
  2. Look for a way to open the changes in VS Code.
  3. Note it's no longer next to "Create PR" — you must open the Changes tab, click the small app-icon button, and choose "Visual Studio Code" from the dropdown each time.
Expected behavior

"Open in VS Code" (or last-used editor) should be a single click accessible from the main session action bar, as it was before, or the dropdown should remember/default to the last-selected app.

Additional context

OS: Windows

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Windows 1.0.80 flow with a session containing uncommitted changes, then trace the session action bar and Changes-panel "Open in..." control. Done means restoring a one-click VS Code or last-used-editor action, or making the dropdown remember the selection, with the affected flow covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell, vscode
Domain
cli, developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.