continuedev / continuedev/continue
Trigger Key for autocomplete suggestions not working
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
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
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
- set "editor.inlineSuggest.enabled": false in your settings.json file
- set a keyboard shortcut (Ctrl + K, S) for editor.action.inlineSuggest.trigger (I chose "Alt+=")
- go to some code in the editor, and mess around, noticing that code complete doesn't work.
- press your trigger key - there should be a suggestion
- it now sticks on as if your trigger key is stuck down
Log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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