Describe the feature or problem you'd like to solve
Currently, when /ide is used to connect Copilot CLI to VS Code, messages typed in the CLI appear in VS Code chat, but messages sent from VS Code chat do not appear in the CLI console. This makes it impossible to use both interfaces together in the same session.
Proposed solution
Both CLI and VS Code chat should act as equal input/output surfaces for the same session — messages from either side should be visible or processed from both.
Suggested Approach - Route VS Code chat inputs through the active /ide-connected CLI session so both
surfaces share a single message queue.
Example prompts or workflows
Power users want to combine CLI capabilities (shell execution, /fleet, file tools, terminal access) with VS Code chat's inline editor integration (code lens, diff view, editor context) in the same working session without losing context.
Additional context
No response
Describe the feature or problem you'd like to solve
Currently, when /ide is used to connect Copilot CLI to VS Code, messages typed in the CLI appear in VS Code chat, but messages sent from VS Code chat do not appear in the CLI console. This makes it impossible to use both interfaces together in the same session.
Proposed solution
Both CLI and VS Code chat should act as equal input/output surfaces for the same session — messages from either side should be visible or processed from both.
Suggested Approach - Route VS Code chat inputs through the active
/ide-connected CLI session so bothsurfaces share a single message queue.
Example prompts or workflows
Power users want to combine CLI capabilities (shell execution, /fleet, file tools, terminal access) with VS Code chat's inline editor integration (code lens, diff view, editor context) in the same working session without losing context.
Additional context
No response