-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Open
Labels
area:configurationRelates to configuration optionsRelates to configuration optionskind:bugIndicates an unexpected problem or unintended behaviorIndicates an unexpected problem or unintended behavior
Description
Description
When using config.yaml (the default for new installations), workspace .continuerc.json files are completely ignored. Only users with config.json can use workspace-level configuration.
Location
core/config/yaml/loadYaml.ts-loadContinueConfigFromYamlfunctioncore/config/load.ts-loadContinueConfigFromJsonfunction
Problem
The JSON config loading path calls getWorkspaceRcConfigs(ide) to load and merge .continuerc.json files from workspace directories:
// In loadContinueConfigFromJson (load.ts)
const workspaceConfigs = await getWorkspaceRcConfigs(ide);
// ... then merges them into the configThe YAML config loading path has no equivalent - it never calls getWorkspaceRcConfigs:
// In loadContinueConfigFromYaml (loadYaml.ts)
// No call to getWorkspaceRcConfigs anywhere in the functionImpact
- Users with
config.yaml(the default) cannot use.continuerc.jsonfor per-repo settings - This is a significant feature gap between the two config formats
- Documentation about
.continuerc.jsondoesn't mention this limitation
Expected behavior
Both config paths should load and merge .continuerc.json files from workspace directories.
Workaround
Rename ~/.continue/config.yaml to config.yaml.bak and create a ~/.continue/config.json instead.
Metadata
Metadata
Assignees
Labels
area:configurationRelates to configuration optionsRelates to configuration optionskind:bugIndicates an unexpected problem or unintended behaviorIndicates an unexpected problem or unintended behavior
Type
Projects
Status
Todo