[Continue CLI] Fatal error: Cannot read properties of undefined (reading 'startsWith')

[amrelhusseiny]

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 believe this is a bug. I'll try to join the Continue Discord for questions
• 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: WSL2.0 ( Ubuntu 22.04.5 LTS )
• Continue version: 1.4.29
• IDE version: cn 1.4.29
• Model: gpt-5-mini, but also GPT-4.1 and Claude Opus
• config:

config.yaml
name: Local Assistant
version: 1.0.0
schema: v1
models:
    # claude model
  - name: "Claude opus-4"
    provider: anthropic
    model: claude-opus-4
    apiKey: xxxx
    apiBase: xxxx

    # claude model
  - name: "Claude sonnet-4"
    provider: anthropic
    model: claude-sonnet-4
    apiKey: xxxx
    apiBase: xxxx

  # openai model
  - name: "Gpt-4.1"
    provider: azure
    model: gpt-4.1
    apiKey: xxxx
    apiBase: xxxx
    requestOptions:
      headers:
        Content-Type: application/json
  
  - name: "gpt-5-mini"
    provider: azure
    model: gpt-5-mini
    apiKey: xxxx
    apiBase: xxxx
    requestOptions:
      headers:
        Content-Type: application/json

context:
  - provider: code
  - provider: docs
  - provider: diff
  - provider: terminal
  - provider: problems
  - provider: folder
  - provider: codebase
  - provider: web
  - provider: search
  - provider: url

Description

Our company private setup only enables us to use Continue.dev, and i need CLI , so its the perfect time to release CLI,

however I am facing the following issue :

with GPT-5-Mini thrugh our own custom baseURL,

Error :

$ cn --config config.yaml -v

Verbose logging enabled (session: eebcc367)
Logs: /home/xxx/.continue/logs/cn.log
Filter this session: grep '\[eebcc367\]' /home/xxxx/.continue/logs/cn.log
**Fatal error: Cannot read properties of undefined (reading 'startsWith')**

To reproduce

No response

Log output

$ cat  /home/vnet/.continue/logs/cn.log
2025-08-21 22:35:15.220 [e2eb4be8] [debug]: Verbose logging enabled
2025-08-21 22:36:26.255 [d3f4ab29] [debug]: Verbose logging enabled
2025-08-21 22:39:14.212 [4cf7e524] [debug]: Verbose logging enabled
2025-08-21 22:45:36.482 [bad10509] [debug]: Verbose logging enabled
2025-08-21 22:49:06.226 [071b23f4] [debug]: Verbose logging enabled
2025-08-21 22:54:34.722 [3df30bf1] [debug]: Verbose logging enabled
2025-08-21 22:57:58.939 [80f940e5] [debug]: Verbose logging enabled
2025-08-21 22:58:47.112 [c3184cb8] [debug]: Verbose logging enabled
2025-08-21 23:00:05.457 [9f64c25f] [debug]: Verbose logging enabled
2025-08-21 23:01:23.082 [09341f93] [debug]: Verbose logging enabled
2025-08-21 23:03:48.582 [2bfc82df] [debug]: Verbose logging enabled
2025-08-21 23:08:19.190 [821cce1b] [debug]: Verbose logging enabled
2025-08-21 23:08:47.655 [a90ea781] [debug]: Verbose logging enabled
2025-08-21 23:10:51.150 [ffc21eda] [debug]: Verbose logging enabled
2025-08-21 23:14:45.763 [59fc831b] [debug]: Verbose logging enabled
2025-08-21 23:27:38.217 [eebcc367] [debug]: Verbose logging enabled

[brainless]

Seems related to #7316