github / github/app

CAPIError 400 invalid message content type <nil>

Open
#2,140 4 comments 1 reaction 0 assignees View on GitHub
Bugs
Dominant language
No language data
Stars
2.1k
Forks
153
PR merge metrics
No merged PRs in 30d

Description

### Short summary

When using a local model (seems to be any model loaded with Ollama), after one response from the model, any subsequent requests will instantly error with the following error: CAPIError 400 invalid message content type

### Affected version or release

v1.0.25

### Installation context

Installed on Windows 11 desktop, private repo (can provide if needed)

### What happened?

Trying to use a local model served by Ollama, getting the following error after one response from the model:

`CAPIError 400 invalid message content type `

Seems to happen with any model loaded in Ollama that supports tool calling - attempted with `gpt-oss:20b` and `empero-ai/Qwable-9B-Claude-Fable-5-GGUF` (from huggingface) models.

I haven't found any relevant errors in any Github issues, nor any relevant search results. There isn't any workaround except for starting a new session, where I can only make one request before getting the error again.

### Steps to reproduce

1. Add local Ollama provider with any model that supports tool calling
2. In Copilot app, make any request in a new session
3. After first response from the model, make another request
4. See error

### Expected behavior

Subsequent requests should be attempted and respond as normal without errors

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the Copilot app using an Ollama model with tool-calling support, then trace how the second request is assembled after the first response. Focus on the message content that becomes nil and verify that repeated requests complete normally without restarting the session.

Written by the indexing model from the issue text.

Assessment

Tech stack
ollama
Domain
ai, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.