VS Code extension globally binds `Ctrl-K Ctrl+C` to open Continue Config

[one-lithe-rune]

Before submitting your bug report

• [X] I believe this is a bug. I'll try to join the Continue Discord for questions
• [X] I'm not able to find an open issue that reports the same bug
• [X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Linux (OpenSUSE Tumbleweed/Plasma 6)
- Continue: v0.9.118
- IDE: VSCode 1.88.1
- Model: N/A

Description

By default Ctrl+K Ctrl+C is bound in Visual Code to comment out code, with a condition of it being active only within a non-readonly editor tab.

This is a reasonably common operation for me when iterating over my code.

However Continue also adds a binding for Ctrl+K Ctrl+C to open its config file, but with no condition at all. This means it takes priority over editor tab specific bindings.

IMO you should at least restrict this to being within the Continue panel. Ideally there probably shouldn't be an automatic key binding setup by Continue for this at all, as changing the config shouldn't really be a common operation once you have it set up, and it is easily accessed from the UI anyway.

If I disable Continue the key binding is removed. If I re-enable Continue the key binding is re-added.

Screenshot of keybindings for Ctrl + K, Ctrl + C with Continue Enabled:

To reproduce

1. Enable Continue extension in VS Code.
2. Open a file with some code in a language of your choice.
3. Select some code in the editor tab for that file.
4. Do Ctrl+K Ctrl+C.
5. Continue config file is opened, rather than the selected code being commented out.

Log output

N/A