Describe the feature or problem you'd like to solve
Right now when starting copilot CLI there is no way to automatically connect to your IDE without manually using the /ide command each time, this wastes time and can often be forgotten leading to a disjoined experience between your IDE and the CLI.
Proposed solution
My proposal is to add a new flag to the coilot CLI that (if set) will automatically connect the copilot CLI to your IDE.
Example prompts or workflows
copilot --ide-connect <workspace path>
This would auto connect copilot to your IDE, if you supply the workspace path then it would use that without further prompt, if not supplied and there are multiple IDE workspaces available then the normal prompt window would appear (as it does currently when using the /ide command).
Additional context
--ide-connect <workspace path> Automatically connect CoPilot CLI to the IDE, if workspace path is supplied then the IDE for that workspace will be selected.
Describe the feature or problem you'd like to solve
Right now when starting copilot CLI there is no way to automatically connect to your IDE without manually using the /ide command each time, this wastes time and can often be forgotten leading to a disjoined experience between your IDE and the CLI.
Proposed solution
My proposal is to add a new flag to the coilot CLI that (if set) will automatically connect the copilot CLI to your IDE.
Example prompts or workflows
copilot --ide-connect <workspace path>This would auto connect copilot to your IDE, if you supply the workspace path then it would use that without further prompt, if not supplied and there are multiple IDE workspaces available then the normal prompt window would appear (as it does currently when using the /ide command).
Additional context