Skip to content

Add Project-Specific config.json Files #4720

@lisyoen

Description

@lisyoen

Validations

  • I believe this is a way to improve. I'll try to join the Continue Discord for questions
  • I'm not able to find an open issue that requests the same enhancement

Problem

The config.json file located under the USERPROFILE directory cannot be applied on a per-project basis. It would be beneficial to use different config.json files for each project. To achieve this, it seems necessary to separate the model's API key into a separate configuration file (apikey.json).

Solution

Use the Project/.continue/config.json file as the primary configuration.
Apply the model-specific API keys written in USERPROFILE/.continue/apikey.json. This approach is similar to how .prompt files are handled.

Metadata

Metadata

Assignees

Labels

area:configurationRelates to configuration optionskind:enhancementIndicates a new feature request, imrovement, or extensionneeds-triageos:windowsHappening specifically on Windows

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions