Summary
PR #11935 added support for .continue/configs/ as a third directory (alongside .continue/agents/ and .continue/assistants/) for loading local config profiles.
Feature Description
- YAML files placed in
.continue/configs/ (workspace or global) are now discovered, watched, and loaded as local profiles
- This enables version-controlled, workspace-level configuration profiles that can be shared with the team
- The feature mirrors the existing pattern of
.continue/agents/ and .continue/assistants/ directories
Documentation Needed
- Update the configuration documentation (
customize/deep-dives/configuration.mdx) to mention the .continue/configs/ directory
- Document that placing YAML config files in
.continue/configs/ (workspace root) will make them appear as selectable local profiles
- Document that file creation/deletion in this directory triggers config reload automatically
- Clarify the difference between:
~/.continue/config.yaml - user-level global configuration
.continue/configs/ - workspace-level config profiles (version-controlled)
Related PR
#11935
Generated with Continue
Co-Authored-By: Continue noreply@continue.dev
Co-authored-by: bekahhw rhawrot@gmail.com
Summary
PR #11935 added support for
.continue/configs/as a third directory (alongside.continue/agents/and.continue/assistants/) for loading local config profiles.Feature Description
.continue/configs/(workspace or global) are now discovered, watched, and loaded as local profiles.continue/agents/and.continue/assistants/directoriesDocumentation Needed
customize/deep-dives/configuration.mdx) to mention the.continue/configs/directory.continue/configs/(workspace root) will make them appear as selectable local profiles~/.continue/config.yaml- user-level global configuration.continue/configs/- workspace-level config profiles (version-controlled)Related PR
#11935
Generated with Continue
Co-Authored-By: Continue noreply@continue.dev
Co-authored-by: bekahhw rhawrot@gmail.com