Skip to content

Ctrl+Backspace to stop generation overrides standard word-delete in chat input #12924

Description

@datOneperson

Before submitting your bug report

Relevant environment info

- OS: Windows
- Continue version: 2.0.0
- IDE version: vs code 1.126.0 
- Model: qwen3-coder-next
- config:
  
name: Main Config
version: 1.0.0
schema: v1
models:
  - name: qwen3-coder-next
    provider: ollama
    model: qwen3-coder-next
    roles:
      - chat
      - edit
      - apply
  - name: Qwen2.5-Coder 1.5B
    provider: ollama
    model: qwen2.5-coder:1.5b-base
    roles:
      - autocomplete
  - name: Nomic Embed
    provider: ollama
    model: nomic-embed-text:latest
    roles:
      - embed

  
  OR link to agent in Continue hub:

Description

Ctrl+Backspace. This shortcut is captured globally within the chat input field, which conflicts with the standard OS/editor behavior of Ctrl+Backspace deleting the word to the left of the cursor.

Expected behavior:
Ctrl+Backspace should only trigger Stop when the input field is not focused, or ideally shouldn't hijack a standard text-editing shortcut at all — similar to how #10647 flagged that Ctrl+Shift+Backspace ("Reject Diff") shouldn't override IntelliJ's native shortcut when there's no diff to reject. In this case, Stop should not override basic word-delete in the input box, especially since the two actions have no relationship to each other from the user's perspective.

Workaround: none currently — there doesn't appear to be a config.yaml or keybinding entry to remove/rebind this, since it isn't registered as a normal VS Code keybinding but instead handled inside the webview itself.

To reproduce

Steps to reproduce:

  1. Open the Continue chat panel and send a message so a response starts streaming.
  2. While the response is still streaming, click into the chat input box and try to use Ctrl+Backspace to delete a word you've typed.
  3. Instead of deleting a word, it triggers the Stop action.

Log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:chatRelates to chat interfaceide:vscodeRelates specifically to VS Code extensionkind:bugIndicates an unexpected problem or unintended behavioros:windowsHappening specifically on Windows

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions