Repository navigation
Continue dev plugin: autocompletion is making VS-Code slow #5055
Description
Before submitting your bug report
- I believe this is a bug. I'll try to join the Continue Discord for questions
- 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:20.04
- Continue version: v1.0.5
- IDE version: 1.99.0
- Model: Codestral
- config:
name: Local Assistant
version: 1.0.0
schema: v1
models:
- name: Gemini 2.0 Flash
provider: gemini
model: gemini-2.0-flash
apiKey: xxx...
- name: Codestral
provider: mistral
model: codestral-latest
apiKey: yyy...
roles:
- autocomplete
defaultCompletionOptions:
temperature: 0.3
stop:
- "\n"
rules:
- Give concise responses
- Always assume TypeScript rather than JavaScript
context:
- provider: code
- provider: docs
- provider: diff
- provider: terminal
- provider: problems
- provider: folder
- provider: codebase
Description
VS Code became very laggy when continue dev plugin is enabled, and I'm writing something to a file, and became normal when I disable the plugin, so the problem is with the autocomplete.
For example, while editing a file, saving a document (Ctrl + s) will not work only after multiple attempts, same for copying and pasting (Ctrl + c, Ctrl + v).
The inline suggestions and continue keep loading (see below picture):
To reproduce
No response
Log output
Reacted by Abdennacer LACHIHEB, Abdennacer LACHIHEB, RiverAge, Minwoo 'Charlie' Choi, Black Binary, Alan Huang, anderk222, Atsushi Koge, David, Eric Foley and 3 more
Activity
[-]Continue dev plugin is making vscode slow[/-][+]Continue dev autocmplete plugin is making vscode slow[/+][-]Continue dev autocmplete plugin is making vscode slow[/-][+]Continue dev plugin: autocompletion is making VS-Code slow[/+]exxocism commentedon Apr 9, 2025
Continue is cool, but It's so painful experience :(
d4rkc0de commentedon Apr 9, 2025
Same issue on my side.
I use qwen2.5-coder:1.5b with ollama for autocomplete though.
ShaySheng commentedon Apr 9, 2025
I use
"editor.inlineSuggest.enabled": falseand bindcommand + Htoeditor.action.inlineSuggest.trigger.This way I could use autocompletion whenever I want.
AIxHunter commentedon Apr 9, 2025
@ShaySheng Thanks that partially helps, but I still prefer the default autocomplete without any biding, it helps accelerate my coding and writing
AwaisBinKaleem commentedon Aug 5, 2025
very slow with OLLAMA
bdougie commentedon Aug 8, 2025
Triaging issues and linking some that could be similar.
rkmax commentedon Sep 4, 2025
I stopped using continue about six months ago because of this lag issue. Yesterday I tried using it again, but the problem still exists. Unfortunately, I have deactivated it again.
sestinj commentedon Sep 12, 2025
Hey @rkmax curious to know more about your setup. Was this with an Ollama model? We have fixes coming for Ollama performance improvement, but it would be good to know if this is something else
mike-pt commentedon Oct 8, 2025
For me some times it autocomplete, other times it does not, or I guess its just taking way to long to show anything, because if I wait for some time eventually it seems to suggest something but its just very slow
Tested with
qwen-2.5-coder:7b and qwen2.5-coder:1.5b (ollama) and also gemini-flash-2.0
On Macbook Pro M4 Max 48GB and I'm only using the autocomplete option no models assigned to chat.
JoschD commentedon Nov 14, 2025
I ran into the same issue it seems, but was able to improve the behavior by increasing the timeouts in the continue.dev settings (you have to scroll down on the main settings page):
Autocomplete Timeout (ms): 350
Autocomplete Debounce (ms): 500
While still not as smooth as e.g. copilot autocomplete, I can now get consistent (and usable) suggestions.
Model: qwen-coder:1.5b
Machine: Macbook Pro M4 Max
github-actions commentedon Feb 13, 2026
This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.
EnzoPV25 commentedon Feb 19, 2026
Hi, same problem here, when continue is enabled VScode becomes really slow, specifically when saving files where it will take several seconds / attempts to save correctly the file... That's sad
github-actions commentedon May 21, 2026
This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.
EnzoPV25 commentedon May 21, 2026
Any updates on this ?
github-actions commentedon Aug 20, 2026
This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.
github-actions commentedon Aug 31, 2026
This issue was closed because it wasn't updated for 10 days after being marked stale. If it's still important, you are welcome to leave a comment and this will keep the issue open. However please note that this repo is no longer being actively maintained.
M3mberTM commentedon Oct 29, 2026
I mean, this isn't a fix but I noticed that using higher debounce for the autocomplete helps a lot with this. I had mine at 150 before, and it was freezing as you guys are saying. I set it to twice that and now it doesn't seem to freeze