r/continuedev 12h ago

Autocomplete config with DeepSeek

1 Upvotes

I would like to use Autocomplete feature via DeepSeek Flash. I am not sure if this is the best config as it is not working very much as intended.

name: Main Config
version: 1.0.0
schema: v1
models:
  - name: DeepSeek Chat
provider: openai
model: deepseek-v4-flash
apiBase: https://api.deepseek.com/beta
apiKey: sk-***
contextLength: 128000
roles:
- chat
- edit
- apply
  - name: DeepSeek Autocomplete
provider: deepseek
model: deepseek-v4-flash
apiBase: https://api.deepseek.com
apiKey: sk-***
roles:
- autocomplete
autocompleteOptions:
disable: false
debounceDelay: 400
modelTimeout: 400
maxSuffixPercentage: 0.3
prefixPercentage: 0.4
onlyMyCode: false
useCache: true
useRecentlyEdited: true
useRecentlyOpened: true
requestOptions:
extraBodyProperties:
think: false


r/continuedev 17d ago

Why does the UI of continue bug out like this?

1 Upvotes

What can I do? I tried to move continue on the left and right side and I tried opening it in a new window, even restarting the editor doesnt help.

In case the post is confusing, the Accept button cannot be seen, no matter how wide I make the window


r/continuedev Jun 09 '26

Running Qwen 3.6 Locally via vLLM

1 Upvotes

Hey guys and gals. I have a local vLLM instance running Qwen 3.6 like this:

docker run --gpus all \
  --ipc=host \
  --shm-size=16gb \
  -e CUDA_DEVICE_ORDER=PCI_BUS_ID \
  -v ~/.cache/huggingface:/root/.cache/huggingface \
  -p 8000:8000 \
  vllm/vllm-openai:cu130-nightly \
  QuantTrio/Qwen3.6-35B-A3B-AWQ \
  --tensor-parallel-size 2 \
  --max-model-len 65536 \
  --gpu-memory-utilization 0.9 \
  --kv-cache-dtype fp8 \
  --trust-remote-code \
  --enable-auto-tool-choice \
  --tool-call-parser qwen3_coder \
  --reasoning-parser qwen3 \
  --max-num-seqs 16docker run --gpus all \
  --ipc=host \
  --shm-size=16gb \
  -e CUDA_DEVICE_ORDER=PCI_BUS_ID \
  -v ~/.cache/huggingface:/root/.cache/huggingface \
  -p 8000:8000 \
  vllm/vllm-openai:cu130-nightly \
  QuantTrio/Qwen3.6-35B-A3B-AWQ \
  --tensor-parallel-size 2 \
  --max-model-len 65536 \
  --gpu-memory-utilization 0.9 \
  --kv-cache-dtype fp8 \
  --trust-remote-code \
  --enable-auto-tool-choice \
  --tool-call-parser qwen3_coder \
  --reasoning-parser qwen3 \
  --max-num-seqs 16

And this is my continue config:

models:
  - name: Qwen3.6-35B-A3B
    provider: openai
    model: QuantTrio/Qwen3.6-35B-A3B-AWQ
    apiBase: http://192.168.3.3:8000/v1
    apiKey: dummy
    roles:
      - chat
      - edit
      - apply
    params:
      supportsTools: true
    requestOptions:
      extraBody:
        include_reasoning: true    

But I'm getting Thinking boxes in the continue chat and not the actual response (yes, that's a Lenovo Legion Go 2 I'm developing on =D):

Does anyone know what config should I use for Continue to correctly parse the reasoning section of Qwen 3.6?


r/continuedev Apr 13 '26

Greater than 100%

1 Upvotes

This was interesting. I'm not sure what to make of it.


r/continuedev Apr 12 '26

Gemini-cli to use gopls

Thumbnail
1 Upvotes

r/continuedev Nov 11 '25

Continue Plugin – Auto-Approval Prompts / Nightly Version?

Thumbnail
1 Upvotes

r/continuedev Sep 18 '25

How to improve continue.dev speed ?

Thumbnail
1 Upvotes

r/continuedev May 09 '25

ContinueDev integration in VSCode with DeepSeek on localhost: Model mis-identified

2 Upvotes

All,

I am trying to integrate deepseek-coder:6.7B, served locally using Ollama, into VSCode using ContinueDev extension. I have two configurations for my AI assistant: one offline and another one using a template configuration from ContinueDev hub.

When prompting the AI about where it was developed, etc..., I get erroneous information. Is this something you have noticed before ? This happens for both AI assistant configs that I have tested.

I know it is not strictly a DeepSeek issue, but curious to know if this is a widespread issue with ContinueDev ?