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: README.md
+31-25Lines changed: 31 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,49 +26,55 @@
26
26
27
27
<p></p>
28
28
29
-
29
+
## Easily understand code sections
30
30
31
-
</div>
31
+
32
+
33
+
VS Code: `cmd+L` (MacOS) / `ctrl+L` (Windows)
34
+
35
+
JetBrains: `cmd+J` (MacOS) / `ctrl+J` (Windows)
36
+
37
+
## Tab to autocomplete code suggestions
38
+
39
+
32
40
33
-
## Task and tab autocomplete
41
+
VS Code: `tab` (MacOS) / `tab` (Windows)
34
42
35
-
### Answer coding questions
43
+
JetBrains: `tab` (MacOS) / `tab` (Windows)
36
44
37
-
Highlight + select sections of code and ask Continue for another perspective
45
+
## Refactor functions where you are coding
38
46
39
-
- “what does this forRoot() static function do in nestjs?”
40
-
- “why is the first left join in this query necessary here?”
41
-
- “how do I run a performance benchmark on this rust binary?”
47
+
42
48
43
-
### Edit in natural language
49
+
VS Code: `cmd+I` (MacOS) / `ctrl+I` (Windows)
44
50
45
-
Highlight + select a section of code and instruct Continue to refactor it
51
+
JetBrains: `cmd+I` (MacOS) / `ctrl+I` (Windows)
46
52
47
-
- “/edit rewrite this to return a flattened list from a 3x3 matrix”
48
-
- “/edit refactor these into an angular flex layout on one line"
49
-
- “/edit define a type here for a list of lists of dictionaries”
53
+
## Ask questions about your codebase
50
54
51
-
### Generate files from scratch
55
+
52
56
53
-
Open a blank file and let Continue start new Python scripts, React components, etc.
57
+
VS Code: `@codebase` (MacOS) / `@codebase` (Windows)
54
58
55
-
- “/edit get me started with a basic supabase edge function”
56
-
- “/edit implement a c++ shortest path algo in a concise way”
57
-
- “/edit create a docker compose file with php and mysql server"
59
+
JetBrains: Support coming soon
58
60
59
-
### And much more!
61
+
##Quickly use documentation as context
60
62
61
-
- Try out [experimental support for local tab autocomplete](https://continue.dev/docs/walkthroughs/tab-autocomplete) in VS Code
62
-
- Use [built-in context providers](https://continue.dev/docs/customization/context-providers#built-in-context-providers) or create your own [custom context providers](https://continue.dev/docs/customization/context-providers#building-your-own-context-provider)
63
-
- Use [built-in slash commands](https://arc.net/l/quote/zbhwfjmp) or create your own [custom slash commands](https://continue.dev/docs/customization/slash-commands#custom-slash-commands)
63
+
64
+
65
+
VS Code: `@docs` (MacOS) / `@docs` (Windows)
66
+
67
+
JetBrains: `@docs` (MacOS) / `@docs` (Windows)
68
+
69
+
</div>
64
70
65
71
## Getting Started
66
72
67
-
####Download for [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains](https://plugins.jetbrains.com/plugin/22707-continue-extension)
73
+
### Download for [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains](https://plugins.jetbrains.com/plugin/22707-continue-extension)
68
74
69
-
You can try out Continue for free using a proxy server that securely makes calls with our API key to models like GPT-4, Gemini Pro, and Phind CodeLlama via OpenAI, Google, and Together respectively.
75
+
You can try out Continue with our free trial models before configuring your setup.
70
76
71
-
Once you're ready to use your own API key or a different model / provider, press the `+` button in the bottom left to add a new model to your `config.json`. Learn more about the models and providers [here](https://continue.dev/docs/model-setup/overview).
77
+
Learn more about the models and providers [here](https://continue.dev/docs/setup/overview).
Continue can be deeply customized by editing `~/.continue/config.json`(`%userprofile%\.continue\config.json` for Windows) and `config.ts` on your machine. These files are created the first time you run Continue. To open `config.json`, click the gear icon in the bottom right corner of the Continue sidebar.
9
+
Continue can be deeply customized by editing `config.json` and `config.ts` on your machine. You can find these files in the `~/.continue/` directory on MacOS and the `%userprofile%\.continue` directory on Windows. These files are created the first time you run Continue.
10
10
11
11
Currently, you can customize the following:
12
12
13
-
-[Models](../model-setup/select-model.md) and [providers](../model-setup/select-provider.md)
14
-
-[Context Providers](./context-providers.md) - Type '@' to easily add attachments to your prompt. Define which sources you want to reference, including GitHub Issues, terminal output, or automatically retrieved snippets from your codebase.
15
-
-[Slash Commands](./slash-commands.md) - Call custom prompts or programs written with our SDK by typing `/`.
16
-
-[Other Configuration](../reference/config.mdx) - Configure other settings like the system message and temperature.
13
+
-[Models](../setup/select-model.md) and [providers](../setup/select-provider.md)
If you'd like to share Continue configuration with others, you can add a `.continuerc.json` to the root of your project. It has the same JSON Schema definition as `config.json`, and will automatically be applied on top of the local `config.json`.
**TL;DR: Using LLMs as you code can accelerate you if you leverage them in the right situations. However, they can also cause you to get lost and confused if you trust them when you should not. This page outlines when and where we think you should and should not use Continue.**
11
-
:::
9
+
## Easily understand code sections
12
10
13
-
## Introduction
11
+
14
12
15
-
Continue will only be as helpful as the LLM you are using to power the edits and explanations. LLMs sometimes hallucinate, so it might make up a library or invent some syntax that does not exist. If something suggested is not working or seems odd to you, it’s best to double check with a Google search to make sure you are not falling into a rabbit hole.
13
+
- VS Code: `cmd+L` (MacOS) / `ctrl+L` (Windows)
14
+
- JetBrains: `cmd+J` (MacOS) / `ctrl+J` (Windows)
16
15
17
-
As you use Continue more, you will learn when to trust it. A great way to get started is to just play with it and start to get a sense of what works and what does not. Continue always ask you to accept / reject any changes it suggests, so you can always undo if something goes wrong.
16
+
## Tab to autocomplete code suggestions
18
17
19
-
If you are trying to use it for a new task and don’t have a sense of how much Continue can help you complete it, it can often be helpful to start like this:
18
+
20
19
21
-
'Highlight' refers to the act of selecting a text range in a file and pressing 'cmd+shift+M' (Macos) or 'ctrl+shift+M' (Windows) to include it in the Continue chat message.
20
+
- VS Code: `tab` (MacOS) / `tab` (Windows)
21
+
- JetBrains: `tab` (MacOS) / `tab` (Windows)
22
22
23
-
1. Highlight the code section(s) that you don’t understand and type "tell me how this code works" in the input box
24
-
2. If the explanation seems reasonable, then, while still highlighting the code section(s), type "how would you change this code to [INSERT TASK]?"
25
-
3. If this explanation is also pretty good, then, while still highlighting the code section(s), type `/edit [INSERT TASK]`. If you like the suggested diff, use `cmd+shift+enter` to accept the changes.
26
-
4. If it does not work on first attempt, use `cmd+shift+backspace` to reject the changes and try again—often it will make a different suggestion each time
27
-
5. If it is not giving you what you want after another attempt, reject and try again with more specific / clear instructions, articulating exactly what you want it to do and not to do
28
-
6. If this still does not work, then you likely need to break down the task into smaller sub-tasks and ask the LLM to do each of those one at a time or just do it yourself manually
23
+
## Refactor functions where you are coding
29
24
30
-
Remember: You are responsible for all code that you ship, whether it was written by you or by an LLM that you directed. This means it is crucial that you review what the LLM writes. To make this easier, we provide natural language descriptions of the actions the LLM took in the Continue GUI.
25
+
31
26
32
-
## When to use Continue
27
+
- VS Code: `cmd+I` (MacOS) / `ctrl+I` (Windows)
28
+
- JetBrains: `cmd+I` (MacOS) / `ctrl+I` (Windows)
33
29
34
-
Here are tasks that Continue excels at helping you complete:
30
+
## Ask questions about your codebase
35
31
36
-
### Laborious edits
32
+
37
33
38
-
Continue works well in situations where find and replace does not work (i.e. “/edit change all of these to be like that”)
34
+
- VS Code: `@codebase` (MacOS) / `@codebase` (Windows)
35
+
- JetBrains: Support coming soon
39
36
40
-
Examples
37
+
## Quickly use documentation as context
41
38
42
-
- "/edit Use 'Union' instead of a vertical bar here"
43
-
- “/edit Make this use more descriptive variable names”
39
+
44
40
45
-
### Writing files from scratch
41
+
- VS Code: `@docs` (MacOS) / `@docs` (Windows)
42
+
- JetBrains: `@docs` (MacOS) / `@docs` (Windows)
46
43
47
-
Continue can help you get started building React components, Python scripts, Shell scripts, Makefiles, unit tests, etc.
44
+
## Kick off actions with slash commands
48
45
49
-
Examples
46
+
50
47
51
-
-“/edit write a python script to get posthog events"
52
-
-“/edit add a react component for syntax highlighted code"
48
+
-VS Code: `/edit` (MacOS) / `/edit` (Windows)
49
+
-JetBrains: `/edit` (MacOS) / `/edit` (Windows)
53
50
54
-
### Creating boilerplate from scratch
51
+
Learn more about slash commands [here](./customization/slash-commands.md)
55
52
56
-
Continue can go even further. For example, it can help build the scaffolding for a Python package, which includes a typer cli app to sort the arguments and print them back out.
53
+
## Add classes, files, and more to context
57
54
58
-
Examples
55
+
59
56
60
-
-“/edit use this schema to write me a SQL query that gets recently churned users”
61
-
-“/edit create a shell script to back up my home dir to /tmp/"
57
+
-VS Code: `@files` (MacOS) / `@files` (Windows)
58
+
-JetBrains: `@files` (MacOS) / `@files` (Windows)
62
59
63
-
### Fix highlighted code
60
+
Learn more about context providers [here](./customization/context-providers.md).
64
61
65
-
After selecting the code section(s), try to refactor it with Continue (e.g “/edit change the function to work like this” or “/edit do this everywhere”)
62
+
## Understand terminal errors immediately
66
63
67
-
Examples
64
+
68
65
69
-
- “/edit migrate this digital ocean terraform file into one that works for GCP”
70
-
- “/edit rewrite this function to be async”
71
-
72
-
### Ask about highlighted code or an entire file
73
-
74
-
If you don't understand how some code works, highlight it and ask "how does this code work?"
75
-
76
-
Examples
77
-
78
-
- “where in the page should I be making this request to the backend?”
79
-
- “how can I communicate between these iframes?”
80
-
81
-
### Ask about errors
82
-
83
-
Continue can also help explain errors / exceptions and offer possible solutions. When you come across an error / exception in your terminal, press `cmd+shift+r` (MacOS) / `ctrl+shift+r` (Windows). This will throw the stack trace into Continue and ask for it to explain the issue to you.
84
-
85
-
### Figure out what shell command to run
86
-
87
-
Instead of switching windows and getting distracted, you can ask things like "How do I find running process on port 8000?"
88
-
89
-
Examples
90
-
91
-
- "what is the load_dotenv library name?"
92
-
- "how do I find running process on port 8000?"
93
-
94
-
### Ask single-turn open-ended questions
95
-
96
-
Instead of leaving your IDE, you can ask open-ended questions that you don't expect to turn into multi-turn conversations.
97
-
98
-
Examples
99
-
100
-
- “how can I set up a Prisma schema that cascades deletes?”
101
-
- "what is the difference between dense and sparse embeddings?"
102
-
103
-
### Editing small existing files
104
-
105
-
You can highlight an entire file and ask Continue to improve it as long as the file is not too large.
106
-
107
-
Examples
108
-
109
-
- “/edit here is a connector for postgres, now write one for kafka”
110
-
- "/edit Rewrite this API call to grab all pages"
111
-
112
-
### Using context from multiple other files
113
-
114
-
Similar to how you would make changes manually, focus on one file at a time. But if there is key information in other files, highlight those sections of code too to be used as additional context
115
-
116
-
### Tasks with a few steps
117
-
118
-
There are many more tasks that Continue can help you complete. Typically, these will be tasks that don't involve too many steps to complete.
119
-
120
-
Examples
121
-
122
-
- “/edit make an IAM policy that creates a user with read-only access to S3”
123
-
- “/edit change this plot into a bar chart in this dashboard component”
124
-
125
-
## When to not use Continue
126
-
127
-
Here are tasks that Continue is **not** helpful with today:
128
-
129
-
### Deep debugging
130
-
131
-
If you are 20 minutes into debugging a complicated issue across many files, then Continue won’t be able to help you connect the dots yet. That said, Continue can provide ideas of what you might do at different points if you share what you have figured out along the way and ask for ideas of what to try.
132
-
133
-
### Multi-file edits in parallel
134
-
135
-
At the moment, Continue can only edit one file at a time. If you figure out which files need to change, you can direct Continue to help you change them one at a time though.
136
-
137
-
### Using context of the entire file
138
-
139
-
If files get too large, it can be difficult for Continue to fit them into the limited LLM context windows. Try to highlight the section of code that include the relevant context. It's rare that you need the entire file.
140
-
141
-
### Editing large files
142
-
143
-
Similarly, if you try to edit too many lines at once, you might run into context window limits. It also will likely be very slow to apply the suggestions.
144
-
145
-
### Highlighting really long lines
146
-
147
-
If you highlight very long lines (e.g. a complex SVG), you might also run into issues like those above.
148
-
149
-
### Tasks with many steps
150
-
151
-
There are other tasks that Continue won't be able to take on entirely at once. However, typically, if you figure out how to break the task into sub-tasks, you can get help from Continue with those.
66
+
- VS Code: `cmd+shift+R` (MacOS) / `ctrl+shift+R` (Windows)
**Continue is an open-source autopilot for [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains](https://plugins.jetbrains.com/plugin/22707-continue-extension)—the easiest way to code with any LLM**
12
-
13
-
Many developers have begun to use ChatGPT while coding; however, the experience is painful because of how much copying, pasting, and editing is required to provide the context and incorporate the generated answers into your codebase. Continue eliminates this pain by enabling LLMs to act natively in your IDE as you complete your workflows.
11
+
**Continue keeps developers in flow. Our open-source [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains](https://plugins.jetbrains.com/plugin/22707-continue-extension) extensions enable you to easily create your own modular AI software development system that you can improve.**
14
12
15
13
Some examples of what you can achieve are:
16
14
17
-
-Use cmd/ctrl + I to generate boilerplate code from natural language
18
-
-Use our local tab-autocomplete to get inline suggestions and write boilerplate code quickly
19
-
-Highlight code, describe how to refactor it, and have changes streamed into your editor
20
-
- Ask high-level questions about your codebase, with Continue automatically finding relevant files
21
-
- Quickly generate unit tests for any function or class
22
-
-Ask a quick question to get immediate answers without leaving your editor
23
-
-Have your current changes reviewed for mistakes that the compiler can't catch
24
-
-Type '@' to reference dozens of different sources while communicating with the LLM
Continue lets you do all of this with any LLM, whether open-source, commercial, local, or remote. And we provide numerous points of configuration so that you can customize the extension to fit into your existing workflows.
24
+
Continue enables you to use the right model for the job, whether it's open-source or commercial, running local or remote, and used for chat, autocomplete, or embeddings. And we provide numerous points of configuration, so that you can customize the extension to fit into your existing workflows.
0 commit comments