Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Windows 11 Home
- Continue version: 1.3.29
- IDE version: 1.108.1
- Model: gemini
- config:
  
name: Gemini 2.5 Pro
version: 1.0.0
schema: v1
models:
  - name: Gemini 2.5 Pro
    provider: gemini
    model: gemini-2.5-pro
    apiKey: **hidden**
    roles:
      - chat
      - edit
      - apply
    defaultCompletionOptions:
      contextLength: 1048576
      maxTokens: 65536
    capabilities:
      - tool_use
      - image_input
  

Description

The modifyConfig function, whether placed in config.ts (with a config.js bridge) or directly in config.js, is never executed. The extension seems to ignore the programmatic configuration files.

To reproduce

1. Setup a standard configuration in ~/.continue/ on Windows.
2. Have a working config.yaml with models defined.
3. Create a config.ts and a config.js bridge file to modify the configuration (e.g., by changing a model's title or injecting an API key from process.env).
4. Reload VS Code.
5. Observe that the modifications from modifyConfig are never applied.

Expected behavior
The modifyConfig function should be executed after config.yaml is loaded, allowing for in-memory modification of the configuration.

Key Findings from Debugging:

• The issue occurs even with a pure, dependency-free JavaScript test in config.js.
• All config files are confirmed to be in the correct default directory (~/.continue/).
• No custom continue.configFile path is set in VS Code settings.
• Crucially: If config.ts is renamed or deleted, the extension automatically creates a new, empty config.ts file upon reloading VS Code. This proves the extension is aware of the file's expected presence but fails to actually execute it.

Log output

None available