You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/walkthroughs/tab-autocomplete.md
+22-6Lines changed: 22 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,28 @@
2
2
3
3
Continue now provides support for tab autocomplete in [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains IDEs](https://plugins.jetbrains.com/plugin/22707-continue/edit). We will be greatly improving the experience over the next few releases, and it is always helpful to hear feedback. If you have any problems or suggestions, please let us know in our [Discord](https://discord.gg/vapESyrFmJ).
4
4
5
+
## Setting up with Starcoder 2 7b (recommended)
6
+
7
+
If you want to have the best autocomplete experience, we recommend using Starcoder 2 7b, which is available through [Fireworks AI](https://fireworks.ai/models/fireworks/starcoder-7b). To do this, obtain an API key and add it to your `config.json`:
We recommend setting up tab-autocomplete with a local Ollama instance. To do this, first download the latest version of Ollama from [here](https://ollama.ai). Then, run the following command to download our recommended model:
8
24
9
25
```bash
10
-
ollama run starcoder:3b
26
+
ollama run starcoder2:3b
11
27
```
12
28
13
29
Once it has been downloaded, you should begin to see completions in VS Code.
@@ -21,7 +37,7 @@ All of the configuration options available for chat models are available to use
21
37
"tabAutocompleteModel": {
22
38
"title": "Tab Autocomplete Model",
23
39
"provider": "ollama",
24
-
"model": "starcoder:3b",
40
+
"model": "starcoder2:3b",
25
41
"apiBase": "https://<my endpoint>"
26
42
},
27
43
...
@@ -32,7 +48,7 @@ If you aren't yet familiar with the available options, you can learn more in our
32
48
33
49
### What model should I use?
34
50
35
-
If you are running the model locally, we recommend `starcoder:3b`.
51
+
If you are running the model locally, we recommend `starcoder2:3b`.
36
52
37
53
If you find it to be too slow, you should try `deepseek-coder:1.3b-base`.
38
54
@@ -46,7 +62,7 @@ The following can be configured in `config.json`:
46
62
47
63
### `tabAutocompleteModel`
48
64
49
-
This is just another object like the ones in the `"models"` array of `config.json`. You can choose and configure any model you would like, but we strongly suggest using a small model made for tab-autocomplete, such as `deepseek-1b`, `starcoder-1b`, or `starcoder-3b`.
65
+
This is just another object like the ones in the `"models"` array of `config.json`. You can choose and configure any model you would like, but we strongly suggest using a small model made for tab-autocomplete, such as `deepseek-1b`, `starcoder-1b`, or `starcoder2-3b`.
50
66
51
67
### `tabAutocompleteOptions`
52
68
@@ -70,7 +86,7 @@ This object allows you to customize the behavior of tab-autocomplete. The availa
70
86
"tabAutocompleteModel": {
71
87
"title": "Tab Autocomplete Model",
72
88
"provider": "ollama",
73
-
"model": "starcoder:3b",
89
+
"model": "starcoder2:3b",
74
90
"apiBase": "https://<my endpoint>"
75
91
},
76
92
"tabAutocompleteOptions": {
@@ -93,7 +109,7 @@ Follow these steps to ensure that everything is set up correctly:
93
109
94
110
1. Make sure you have the "Enable Tab Autocomplete" setting checked (in VS Code, you can toggle by clicking the "Continue" button in the status bar).
95
111
2. Make sure you have downloaded Ollama.
96
-
3. Run `ollama run starcoder:3b` to verify that the model is downloaded.
112
+
3. Run `ollama run starcoder2:3b` to verify that the model is downloaded.
97
113
4. Make sure that any other completion providers are disabled (e.g. Copilot), as they may interfere.
98
114
5. Make sure that you aren't also using another Ollama model for chat. This will cause Ollama to constantly load and unload the models from memory, resulting in slow responses (or none at all) for both.
99
115
6. Check the output of the logs to find any potential errors (cmd/ctrl+shift+p -> "Toggle Developer Tools" -> "Console" tab in VS Code, ~/.continue/core.log in JetBrains).
0 commit comments