Describe the feature or problem you'd like to solve
When the Copilot CLI spawns a shell process, I have no way to see or interact with that shell directly, in the event it decides to use one of my tools that functions as a terminal ui. Just today, copilot instructed me to use arrow keys, this is guidance that I cannot follow.
Proposed solution
Add a mechanism for the user to switch to or "alt+tab" to a running agent spawned shell session.
Perhaps, a /shell <shellId> command that swaps focus to the live session, or a tab or split-pane view showing active shell sessions the agent has started.
Example prompts or workflows
The agent is great at knowing what to run but sometimes the best tool for the job is interactive. Right now, the agent must either avoid interactive tools entirely or attempt to puppet them through a text proxy both are worse outcomes than just letting me take the wheel for 5 seconds.
Example workflows this enables:
- "Find me the config file for X"
- "Debug this test failure"
- "Resolve these merge conflicts"
- "Help me set up this project"
- "Show me what's running on this port"
Additional context
No response
Describe the feature or problem you'd like to solve
When the Copilot CLI spawns a shell process, I have no way to see or interact with that shell directly, in the event it decides to use one of my tools that functions as a terminal ui. Just today, copilot instructed me to use arrow keys, this is guidance that I cannot follow.
Proposed solution
Add a mechanism for the user to switch to or "alt+tab" to a running agent spawned shell session.
Perhaps, a
/shell <shellId>command that swaps focus to the live session, or a tab or split-pane view showing active shell sessions the agent has started.Example prompts or workflows
The agent is great at knowing what to run but sometimes the best tool for the job is interactive. Right now, the agent must either avoid interactive tools entirely or attempt to puppet them through a text proxy both are worse outcomes than just letting me take the wheel for 5 seconds.
Example workflows this enables:
Additional context
No response