Describe the feature or problem you'd like to solve
The feature would allow the user to use the same key-bindings of that they were using inside the terminal that launched copilot-cli
Proposed solution
The terminal generally has its own key bindings, but when launching copilot-cli, the latter switches to the keyboard's regular keys.
I find it confusing and it limits the usability of copilot-cli in my case. I expect things running on my terminal to have the same keybindings, so when switch tab or just forgetting that copilot does things differently, I end up closing copilot, interrupting the execution, etc.
I believe that if copilot-cli carried over the same key bindings of the environment it was started from, the user experience would improve and friction in its usage would be reduced.
Example prompts or workflows
Example.
Today, if the user starts copilot-cli from ubuntu's terminal, ctrl+D than shuts down copilot-cli, instead of deleting the next character. Ideally, the behavior is consistent inside and outside copilot-cli.
Additional context
No response
Describe the feature or problem you'd like to solve
The feature would allow the user to use the same key-bindings of that they were using inside the terminal that launched copilot-cli
Proposed solution
The terminal generally has its own key bindings, but when launching copilot-cli, the latter switches to the keyboard's regular keys.
I find it confusing and it limits the usability of copilot-cli in my case. I expect things running on my terminal to have the same keybindings, so when switch tab or just forgetting that copilot does things differently, I end up closing copilot, interrupting the execution, etc.
I believe that if copilot-cli carried over the same key bindings of the environment it was started from, the user experience would improve and friction in its usage would be reduced.
Example prompts or workflows
Example.
Today, if the user starts copilot-cli from ubuntu's terminal,
ctrl+Dthan shuts down copilot-cli, instead of deleting the next character. Ideally, the behavior is consistent inside and outside copilot-cli.Additional context
No response