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
You can easily access your assistant configuration from the Continue Chat sidebar. Open the sidebar by pressing <kbd>cmd/ctrl</kbd> + <kbd>L</kbd> (VS Code) or <kbd>cmd/ctrl</kbd> + <kbd>J</kbd> (JetBrains) and click the Assistant selector above the main chat input. Then, you can hover over an assistant and click the `new window` (hub assistants) or `gear` (local assistants) icon.
9
+
10
+
11
+
12
+
## Hub Assistants
13
+
14
+
Hub Assistants can be managed in [the Hub](https://hub.continue.dev). See [Editing an Assistant](../../hub/assistants/edit-an-assistant.md)
15
+
8
16
## YAML Config
9
17
10
-
Continue can be deeply customized. Local user-level configuration is stored and can be edited in your home directory in `config.yaml`:
18
+
Local user-level configuration is stored and can be edited in your home directory in `config.yaml`:
11
19
12
20
To open `config.yaml`, you can click the "gear" icon in the header of the Continue Chat sidebar to open the settings page, and then click `Open Assistant configuration` to open the file. When editing this file, you can see the available options suggested as you type, or check the reference below.
13
21
14
22
-`~/.continue/config.yaml` (MacOS / Linux)
15
23
-`%USERPROFILE%\.continue\config.yaml` (Windows)
16
24
17
-
To open your configuration file, you can click the "gear" icon in the bottom right corner of the Continue Chat sidebar. When editing this file, you can see the available options suggested as you type, or check the reference below.
18
-
19
25
When you save a config file from the IDE, Continue will automatically refresh to take into account your changes. A config file is automatically created the first time you use Continue, and always automatically generated with default values if it doesn't exist.
20
26
21
27
See the full reference for `config.yaml`[here](../../reference.md).
@@ -49,7 +55,9 @@ Example
49
55
50
56
### `config.ts`
51
57
52
-
To programatically extend `config.json`, you can place a `config.ts` script in same directory as `config.json` and export a `modifyConfig` function, like:
58
+
`config.yaml` or `config.json` can handle the vast majority of necessary configuration, so we recommend using it whenever possible. However, if you need to programmatically extend Continue configuration, you can use a `config.ts` file, placed at `~/.continue/config.ts` (MacOS / Linux) or `%USERPROFILE%\.continue\config.ts` (Windows).
59
+
60
+
`config.ts` must export a `modifyConfig` function, like:
@@ -75,4 +83,4 @@ export function modifyConfig(config: Config): Config {
75
83
}
76
84
```
77
85
78
-
This can be used for slash commands and custom context providers.
86
+
For examples of how to use `config.ts`, see [writing custom slash commands](../tutorials/build-your-own-slash-command.md#custom-slash-commands) or [writing custom context providers](../tutorials/build-your-own-context-provider.mdx).
description: Shortcuts that can be activated by prefacing your input with '/'
4
+
keywords: [slash command, custom commands, step]
5
+
---
6
+
7
+
importTabItemfrom"@theme/TabItem";
8
+
importTabsfrom"@theme/Tabs";
9
+
10
+
11
+
12
+
## Slash commands
13
+
14
+
Slash commands are shortcuts that can be activated by typing '/' in a chat session (press <kbd>cmd/ctrl</kbd> + <kbd>L</kbd> (VS Code) or <kbd>cmd/ctrl</kbd> + <kbd>J</kbd> (JetBrains)), and selecting from the dropdown.
Slash commands can be combined with additional instructions, including [context providers](../context-providers.mdx) or [highlighted code](../../edit/context-selection#highlighted-code).
18
+
19
+
## Prompts
20
+
21
+
### Assistant prompt blocks
22
+
23
+
The easiest way to add a slash command is by adding [`prompt` blocks](../../hub/blocks/block-types.md#prompts) to your assistant, which show up as slash commands in [Chat](../../chat/how-it-works.md).
24
+
25
+
### Prompt files
26
+
27
+
It is also possible to write your own slash command by defining a “.prompt file.” Prompt files can be as simple as a text file, but also include templating so that you can refer to files, URLs, highlighted code, and more.
28
+
29
+
Learn more about prompt files [here](./prompt-files.md)
30
+
31
+
### MCP Server prompts
32
+
33
+
Any prompts provided by [Model Context Protocol](https://modelcontextprotocol.io/introduction) servers are also accessible in chat as Slash Commands. See the [MCP Server Deep Dive](./mcp.mdx) for more details.
Currently all of these are only available in VS Code
11
+
:::
12
+
13
+
To make common use cases even more accessible, we provide a handful of other ways to invoke actions in VS Code.
14
+
15
+
## Quick actions
16
+
17
+
Quick Actions are displayed as buttons above top-level classes and functions in your source code, letting you invoke actions with one click. They will edit that class or function, but nothing outside of it. They can also be customized with [.prompt files](./prompt-files.md) to perform custom actions.
18
+
19
+
20
+
21
+
By default, quick actions are disabled, but can be enabled with the “Continue: Enable Quick Actions” in VS Code settings.
22
+
23
+
## Right click actions
24
+
25
+
Right click actions let you highlight a desired region of code, right click, and then select an action from the dropdown menu.
26
+
27
+
The highlighted code you’ve selected will be included in your prompt alongside a pre-written set of instructions depending on the selected action. This is the only section of code that the model will attempt to edit.
28
+
29
+
Right click actions that generate inline diffs use the same prompt and response processing logic as [Edit](../../edit/how-it-works.md).
30
+
31
+
32
+
33
+
## Debug action
34
+
35
+
The debug action is a special built-in keyboard shortcut in the VS Code extension. Use <kbd>cmd/ctrl</kbd> + <kbd>shift</kbd> + <kbd>R</kbd> to instantly copy the contents of the most recent terminal output into the chat sidebar and get debugging advice. There is no additional, non-visible information sent to the language model.
36
+
37
+
```
38
+
I got the following error, can you please help explain how to fix it?
39
+
40
+
[ERROR_MESSAGE]
41
+
```
42
+
43
+
## Quick fixes
44
+
45
+
Whenever you see red/yellow underlines in your code indicating errors, you can place your cursor nearby and VS Code will display a lightbulb icon. Either clicking the lightbulb or using the keyboard shortcut <kbd>cmd/ctrl</kbd> + <kbd>.</kbd> will show a dropdown menu of quick fixes. One of these will be the “Ask Continue” action. Either click or use <kbd>cmd/ctrl</kbd> + <kbd>.</kbd> again and Continue will attempt to help solve the problem.
46
+
47
+
Similarly to the debug action, quick actions transparently inject a prompt into the chat window. When you select “Ask Continue”, the 3 lines above and below the error are sent to the chat followed by the question “How do I fix the following problem in the above code?: [ERROR_MESSAGE]”.
0 commit comments