-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Describe the feature or problem you'd like to solve
Right now, you can open the terminal in Visual Studio Code, and then when you start a Copilot instance, it will connect to the current Visual Studio Code instance. It would also be nice to have this on an external terminal window, that way it's not using the same resources as Visual Studio Code, as I have seen in very large code bases where Visual Studio Code sometimes has problems with handling multiple files; the CLI is much faster in this when running in a separate terminal. A disadvantage is that you lose the ability to quickly reference code selection or files as you have in the Visual Studio Code context menus.
Proposed solution
Running Copilot CLI in an external terminal offloads AI agent workloads from the VS Code process, which matters most in large codebases where VS Code already struggles with memory and file indexing. Users get a faster, more stable agent experience without competing for the same resources as the editor. It also opens the door for power users who prefer a dedicated terminal workflow.
Example prompts or workflows
No response
Additional context
No response