Mistral API does not accept `reasoning_content` field
メンテナーはふだん 2 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
Start by tracing how the Mistral provider builds assistant messages for the next request, especially messages containing reasoning from the previous response. The issue reports a 422 because reasoning_content is sent as an extra field and suggests Mistral's thinking content format as a possible direction. Done means a follow-up prompt works after a reasoning response.
索引モデルが issue の本文から書いたものです。
説明
To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.
Please avoid AI slops, be concise, and focus on what matters for this issue.
Describe the bug
When working with models provided via Mistral's API that support thinking/reasoning (GLM 5.3, Mistral Large 4, etc) and reasoning is enabled (e.g. reasoning_effort: high), the second prompt send by the user always fails with response status code 422 and message and an error message of the sort:
{"detail":[{"type":"extra_forbidden","loc":["body","messages",2,"assistant","reasoning_content"],"msg":"Extra inputs are not permitted","input":"The user just said \"Hello.\" with no specific task. I should respond briefly and greet them, maybe noting what I can see in their workspace. No need for tools here. Keep it short."}]}
To Reproduce
Steps to reproduce the behavior:
- Select a model hosted by Mistral that supports reasoning (e.g.
mistral/zai-glm-5-3). - Write and send a simple user prompt (e.g. "Hello")
- Wait the model to think and reply (the reply must include a "thought" block).
- Write and send another user prompt (e.g. "Hi again").
Expected behavior
Receive a proper response from the model and resume the conversation.
Doctor
ECA version: 0.166.0
Server cmd: ~/.cache/emacs/eca/eca server
Logged providers:
mistral: API key (XXX**********XXX)
Screenshots
Additional context
I have encountered the same issue with other frameworks and the problem there was caused by Mistral's API not expecting a reasoning_content field, like Deepseek's and OpenAI's APIs. Not sure if that is the proper solution or just a workaround but, it appears that placing reasoning content inside a "thinking" element (seems unique to Mistral's API spec) which is placed inside the content of a regular "assistant" message, works. For example:
{
"model": "mistral-small-latest",
"messages": [
{
"role": "system",
"content": "You are a large language model living in Emacs and a helpful assistant. Respond concisely."
},
{
"role": "user",
"content": "Hello. Please list the files in the current directory and report them to me."
},
{
"role": "assistant",
"tool_calls": [
{
"id": "oagouVY1Z",
"type": "function",
"function": {
"name": "list_directory",
"arguments": "{\"path\": \".\"}"
},
"index": 0
}
],
"content": [
{
"type": "thinking",
"thinking": [
{
"type": "text",
"text": "The user wants me to list the files in the current directory. I need to use the list_directory tool to do this. Since they said \"current directory\", I should use \".\" as the path to represent the current directory."
}
],
"closed": true
}
]
},
{
"role": "tool",
"tool_call_id": "oagouVY1Z",
"content": "..."
}
],
"stream": false,
"tools": [
{
"type": "function",
"function": {
"name": "list_directory",
"description": "List the contents of a specified directory.",
"parameters": {
"type": "object",
"properties": {
"path": {
"description": "Path to the directory. Supports relative paths and '~'.",
"type": "string"
}
},
"required": [
"path"
],
"additionalProperties": false
}
}
}
],
"parallel_tool_calls": true,
"reasoning_effort": "high"
}
- 主要言語
- Clojure
- スター
- 1k
- フォーク
- 82
- 平均マージ
- 2日 2時間
- マージ済み PR（30日）
- 21
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
editor-code-assistant/eca のほかの issue
-
Models doesn't work when fetchModels: false is used対応中かも @zikajk が 9 日前に担当しました。 オープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
editor-code-assistant/eca#661 · 担当者 1 名 ·
メンテナーはふだん 2 日以内に返信
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 74/100
editor-code-assistant/eca#672 ·
メンテナーはふだん 2 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
editor-code-assistant/eca#671 · コメント 2 件 ·
メンテナーはふだん 2 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
editor-code-assistant/eca#670 ·
メンテナーはふだん 2 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 52/100
editor-code-assistant/eca#669 ·
メンテナーはふだん 2 日以内に返信
editor-code-assistant/eca の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
WG adoption
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
メンテナーはふだん 4 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
clojure-emacs/cider#4224 ·
メンテナーはふだん 3 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100