Error handling model response: Cannot read properties of undefined (reading 'call')

[casperwahl]

Before submitting your bug report

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

Relevant environment info

- OS: macOS Tahoe 26.0.1
- Continue version: 1.2.10
- IDE version: vs code 1.101.1
- Model: Azure OpenAI GPT-5-chat and Azure OpenAI GPT-4o
- config:
  
name: Local Config
version: 1.0.0
schema: v1
models:
  - name: GPT-5
    provider: azure
    model: gpt-5-chat
    apiKey: xyz
    apiBase: https://xyz.cognitiveservices.azure.com/
    deployment: gpt-5-chat
  - name: GPT-4o
    provider: azure
    model: gpt-4o
    apiKey: xyz
    apiBase: https://xyz.openai.azure.com/

Description

Everytime I attempt to chat with the extension I get an error. I've tried different versions of the extension in vscode, tried reinstalling as well as removing the ~/.continue/ folder with no success.

To reproduce

1. Open Continue vscode extension
2. Send a message

Log output

console.ts:137 [Extension Host] Error handling webview message: {
  "msg": {
    "messageId": "482ef752-8993-4aae-ac92-5bfb2cd1ffa5",
    "messageType": "llm/streamChat",
    "data": {
      "completionOptions": {
        "reasoning": false
      },
      "title": "GPT-5",
      "messages": [
        {
          "role": "system",
          "content": "<important_rules>\n  You are in chat mode.\n\n  If the user asks to make changes to files offer that they can use the Apply Button on the code block, or switch to Agent Mode to make the suggested updates automatically.\n  If needed concisely explain to the user they can switch to agent mode using the Mode Selector dropdown and provide no other details.\n\n  Always include the language and file name in the info string when you write code blocks.\n  If you are editing \"src/main.py\" for example, your code block should start with ' src/main.py'\n\n  When addressing code modification requests, present a concise code snippet that\n  emphasizes only the necessary changes and uses abbreviated placeholders for\n  unmodified sections. For example:\n\n   /path/to/file\n  // ... existing code ...\n\n  {{ modified code here }}\n\n  // ... existing code ...\n\n  {{ another modification }}\n\n  // ... rest of code ...\n  \n\n  In existing files, you should always restate the function or class that the snippet belongs to:\n\n   /path/to/file\n  // ... existing code ...\n\n  function exampleFunction() {\n    // ... existing code ...\n\n    {{ modified code here }}\n\n    // ... rest of function ...\n  }\n\n  // ... rest of code ...\n  \n\n  Since users have access to their complete file, they prefer reading only the\n  relevant modifications. It's perfectly acceptable to omit unmodified portions\n  at the beginning, middle, or end of files using these \"lazy\" comments. Only\n  provide the complete file when explicitly requested. Include a concise explanation\n  of changes unless the user specifically asks for code only.\n\n</important_rules>"
        },
        {
          "role": "user",
          "content": "hi"
        }
      ],
      "messageOptions": {
        "precompiled": true
      }
    }
  }
}

TypeError: Cannot read properties of undefined (reading 'call')