Bug: Multiple HTTP context providers only load first one in config.yaml (works correctly in config.json)

[Hondarer]

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 (25H2, 26200.7462)
- Continue version: 1.2.11
- IDE: VS Code
- IDE version: 1.107.1

Description

When defining multiple HTTP context providers in config.yaml, only the first provider appears in the @ mention dropdown. However, the same configuration works correctly in config.json, where all providers are displayed. This appears to be a YAML parser or config loading issue specific to handling duplicate provider: http entries.

Additional Context

• Other context providers (e.g., @code, @docs, @file) work correctly in both config formats
• The issue specifically affects multiple instances of the same provider type
• config.yaml takes precedence over config.json when both are present, preventing the use of config.json as a workaround
• While reverting all settings to config.json (i.e., the deprecated legacy format) would work, this is not a prudent choice
• config.ts has been deprecated, preventing workarounds via TypeScript configuration
• VSCode Extension API workaround is possible but requires users to create custom extensions

To reproduce

Create ~/.continue/config.yaml with multiple HTTP context providers:

context:
  - provider: http
    params:
      url: http://localhost:5000/context
      title: http-provider-5000
      displayTitle: HTTP Provider 5000
      description: Retrieve a context item from custom server 5000
  - provider: http
    params:
      url: http://localhost:5001/context
      title: http-provider-5001
      displayTitle: HTTP Provider 5001
      description: Retrieve a context item from custom server 5001
  - provider: http
    params:
      url: http://localhost:5002/context
      title: http-provider-5002
      displayTitle: HTTP Provider 5002
      description: Retrieve a context item from custom server 5002

1. Reload VS Code
2. Open Continue chat panel
3. Type @ to open context provider dropdown

Expected Behavior

All three HTTP providers should appear in the dropdown:

• HTTP Provider 5000
• HTTP Provider 5001
• HTTP Provider 5002

Actual Behavior

Only "HTTP Provider 5000" appears in the dropdown.

Workaround - config.json works correctly

When using the equivalent configuration in config.json, all three providers display correctly:

{
  "contextProviders": [
    {
      "name": "http",
      "params": {
        "url": "http://localhost:5000/context",
        "title": "http-provider-5000",
        "displayTitle": "HTTP Provider 5000",
        "description": "Custom server on port 5000"
      }
    },
    {
      "name": "http",
      "params": {
        "url": "http://localhost:5001/context",
        "title": "http-provider-5001",
        "displayTitle": "HTTP Provider 5001",
        "description": "Custom server on port 5001"
      }
    },
    {
      "name": "http",
      "params": {
        "url": "http://localhost:5002/context",
        "title": "http-provider-5002",
        "displayTitle": "HTTP Provider 5002",
        "description": "Custom server on port 5002"
      }
    }
  ]
}

With this configuration, all three providers appear correctly in the dropdown.

Log output

[sestinj]

Related Issues

Based on a search of the repository, here are potentially related issues:

Similar YAML Configuration Issues

• Bug: YAML config path does not load workspace .continuerc.json files #9313 - Bug: YAML config path does not load workspace .continuerc.json files
• Empty config.json with valid config.yml breaks config load. Empty json file should be ignored and not parsed. #6148 - Empty config.json with valid config.yml breaks config load (closed)
• Continue is looking for configuration in config.json instead of local .continue/yamls #5817 - Continue is looking for configuration in config.json instead of local .continue/yamls (closed)
• Multiple JSON schema : config-yaml-schema.json #6514 - Multiple JSON schema : config-yaml-schema.json (closed)

Multiple Context Providers Issues

• Multiple context providers in IDEA are not work. #3541 - Multiple context providers in IDEA are not work (closed)
• [CON-260] Support multiple instances of the same context provider in config.json #2002 - Support multiple instances of the same context provider in config.json (closed)
• Postrges context provider can't handle multiple shemas #2823 - Postgres context provider can't handle multiple schemas (closed)

YAML Array/Configuration Issues

• Missing "transform" option in YAML config — always trims autocomplete output #7506 - Missing "transform" option in YAML config (closed)
• config.yaml contextLength is not applied to model #4638 - config.yaml contextLength is not applied to model

General YAML Config vs JSON Config Issues

• Prompt config.yaml vs file.prompt parameter handling #6031 - Prompt config.yaml vs file.prompt parameter handling (closed)
• @Jira context: error "self signed certificate in certificate chain" - lost of global requestOptions used in fetch with YAML config #5484 - @jira context: error with YAML config - lost of global requestOptions used in fetch

The most relevant appears to be #2002 which added support for multiple instances of the same context provider in config.json - this may indicate the YAML parsing doesn't fully implement the same behavior.