Summary
PR #11935 introduced support for .continue/configs/ as a directory for loading local config profiles, but this is not documented.
Missing Documentation
The following needs to be documented:
.continue/configs/ is now a supported directory alongside .continue/agents/ and .continue/assistants/ for loading local config profiles
- YAML files placed in
.continue/configs/ (workspace or global) are discovered, watched, and loaded as local profiles
- This enables version-controlled configs that can be shared with your team
Current Documentation Gap
The existing documentation in docs/customize/deep-dives/configuration.mdx and docs/guides/understanding-configs.mdx only mentions:
~/.continue/config.yaml for user-level configuration
.continue/agents/ for local agents
.continue/assistants/ for local assistants
But .continue/configs/ is not mentioned as a supported location for local config profiles.
Related PR
Suggested Location
docs/customize/deep-dives/configuration.mdx
docs/guides/understanding-configs.mdx
Generated with Continue
Co-Authored-By: Continue noreply@continue.dev
Co-authored-by: bekahhw rhawrot@gmail.com
Summary
PR #11935 introduced support for
.continue/configs/as a directory for loading local config profiles, but this is not documented.Missing Documentation
The following needs to be documented:
.continue/configs/is now a supported directory alongside.continue/agents/and.continue/assistants/for loading local config profiles.continue/configs/(workspace or global) are discovered, watched, and loaded as local profilesCurrent Documentation Gap
The existing documentation in
docs/customize/deep-dives/configuration.mdxanddocs/guides/understanding-configs.mdxonly mentions:~/.continue/config.yamlfor user-level configuration.continue/agents/for local agents.continue/assistants/for local assistantsBut
.continue/configs/is not mentioned as a supported location for local config profiles.Related PR
Suggested Location
docs/customize/deep-dives/configuration.mdxdocs/guides/understanding-configs.mdxGenerated with Continue
Co-Authored-By: Continue noreply@continue.dev
Co-authored-by: bekahhw rhawrot@gmail.com