Skip to content

docs: document local config profiles directory #12474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sarthakNITT wants to merge 5 commits into
base: main
Choose a base branch
from
+33 −0
Open

docs: document local config profiles directory #12474

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a787164
npm i
sarthakNITT Mar 25, 2026
a5de45e
Merge remote-tracking branch 'upstream/main'
sarthakNITT May 22, 2026
1aaef81
fixed issue #12469
sarthakNITT May 22, 2026
5ddf1de
.
sarthakNITT May 22, 2026
caffa8c
copilot suggestion 2
sarthakNITT May 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions docs/customize/deep-dives/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,39 @@ When editing this file, you can see the available options suggested as you type,

See the full reference for `config.yaml` [here](/reference).

### Local Config Profiles

In addition to the main `config.yaml`, you can create multiple local config profiles by adding YAML files to a `.continue/configs/` directory:

- `~/.continue/configs/` for profiles available across all workspaces
- `<workspace>/.continue/configs/` for profiles available only in that workspace

Each `.yaml` or `.yml` file is loaded as a separate local profile and appears in the config selector. Creating, editing, or deleting a file in `.continue/configs/` automatically reloads Continue.

Local profile files use the same YAML schema as `config.yaml`.

Comment thread
sarthakNITT marked this conversation as resolved.
Example (global/user-level `~/.continue/` directory):

```text
.continue/
|-- config.yaml
|-- configs/
| |-- default.yaml
| `-- code-review.yaml
|-- agents/
| `-- local-agent.yaml
`-- assistants/
`-- local-assistant.yaml
```

Continue also discovers YAML profiles from these local directories:

- `<workspace>/.continue/configs/` or `~/.continue/configs/` (`%USERPROFILE%\.continue\configs\` on Windows for global profiles)
- `<workspace>/.continue/agents/` or `~/.continue/agents/` (`%USERPROFILE%\.continue\agents\` on Windows for global profiles)
- `<workspace>/.continue/assistants/` or `~/.continue/assistants/` (`%USERPROFILE%\.continue\assistants\` on Windows for global profiles)

Use `.continue/configs/` for general local config profiles. The `.continue/agents/` and `.continue/assistants/` directories are supported alongside it for existing local agent and assistant profiles in either workspace-local or global Continue directories.

## Legacy Configuration Methods (Deprecated)

<Info>
Expand Down
Loading