Summary
PR #11935 added support for .continue/configs/ as a third directory (alongside .continue/agents/ and .continue/assistants/) for loading local config profiles. YAML files placed in .continue/configs/ (workspace or global) are now discovered, watched, and loaded as local profiles.
What needs to be documented
- Explain that
.continue/configs/ is a valid directory for storing config profile YAML files
- Document the difference between:
~/.continue/config.yaml - main local config file
~/.continue/configs/ - directory for additional config profiles
- Workspace-level
.continue/configs/ directory
- Add examples of how to create and use config profiles in this directory
- Update relevant documentation pages (e.g.,
docs/customize/deep-dives/configuration.mdx, docs/guides/understanding-configs.mdx)
Related PR
Notes
The current documentation at docs/guides/ollama-guide.mdx incorrectly references ~/.continue/configs/config.yaml which appears to be a typo/error - the main config file should be at ~/.continue/config.yaml.
Summary
PR #11935 added support for
.continue/configs/as a third directory (alongside.continue/agents/and.continue/assistants/) for loading local config profiles. YAML files placed in.continue/configs/(workspace or global) are now discovered, watched, and loaded as local profiles.What needs to be documented
.continue/configs/is a valid directory for storing config profile YAML files~/.continue/config.yaml- main local config file~/.continue/configs/- directory for additional config profiles.continue/configs/directorydocs/customize/deep-dives/configuration.mdx,docs/guides/understanding-configs.mdx)Related PR
Notes
The current documentation at
docs/guides/ollama-guide.mdxincorrectly references~/.continue/configs/config.yamlwhich appears to be a typo/error - the main config file should be at~/.continue/config.yaml.