continuedev / continuedev/continue

Trigger Key for autocomplete suggestions not working

Open
#13,242 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
- OS: Ubuntu 24.04
- Continue version: v2.0.0
- IDE version: VS Code 1.136.0
- Model: qwen2.5 Coder
- config:
  
name: Main Config
version: 1.0.0
schema: v1
models:
  - name: Llama 3.1 8B
    provider: ollama
    model: llama3.1:8b
    roles:
      - chat
      - edit
      - apply
#  - name: Qwen2.5-Coder 1.5B
#    provider: ollama
#    model: qwen2.5-coder:1.5b-base
#    roles:
#      - autocomplete
  - name: Local llp
    provider: llama.cpp
    model: qwen
    apiBase: http://127.0.0.1:8080
    roles:
      - autocomplete
  - name: Nomic Embed
    provider: ollama
    model: nomic-embed-text:latest
    roles:
      - embed

  
  OR link to agent in Continue hub:
Description

I'm trying to set a trigger key. I have followed all the instructions according to "How to set a trigger key for Autocomplete suggestions" section at https://github.com/continuedev/continue/blob/main/docs/customize/deep-dives/autocomplete.mdx?utm_source=chatgpt.com, but it seems when I press the trigger key, it essentially turns on full auto mode again, without remembering I only want it triggering on the configured shortcut.

To reproduce
  1. set "editor.inlineSuggest.enabled": false in your settings.json file
  2. set a keyboard shortcut (Ctrl + K, S) for editor.action.inlineSuggest.trigger (I chose "Alt+=")
  3. go to some code in the editor, and mess around, noticing that code complete doesn't work.
  4. press your trigger key - there should be a suggestion
  5. it now sticks on as if your trigger key is stuck down
Log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/customize/deep-dives/autocomplete.mdx and reproduce the issue using editor.inlineSuggest.enabled set to false and the editor.action.inlineSuggest.trigger shortcut in VS Code. Trace the autocomplete trigger behavior and verify that pressing the configured shortcut shows one suggestion without re-enabling continuous inline suggestions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.