Open WebUI Does Not Display Deepseek API Reasoning Content Due to Unsupported reasoning_content Field #3609

New Issue

2025-11-11T15:35:12-06:00

GiteaMirror commented

2025-11-11 15:35:12 -06:00

Originally created by @Lesiuk on GitHub (Feb 5, 2025).

Bug Report

Summary: Open WebUI fails to display Deepseek API's reasoning_content due to field mismatch.

Environment

Installation Method: Docker (replace with your method)
Open WebUI Version: [e.g., v0.3.11]
Ollama (if applicable): [N/A or version]
Operating System: [e.g., Ubuntu 22.04]
Browser: [e.g., Chrome 120.0]

Confirmation:

Read README.md instructions
Latest Open WebUI version
Browser/Docker logs included (if applicable)

Expected Behavior

Reasoning content from Deepseek API should appear in Open WebUI within ``

Thinking…

> tags (e.g., `Okay, ...

`).

Actual Behavior

Reasoning content is not displayed because Deepseek returns it in a reasoning_content field instead of populating content.

Reproduction Steps

Send a request to Deepseek's API (e.g., via Open WebUI).

Observe the API response format:

{  
  "choices": [  
    {  
      "delta": {  
        "reasoning_content": "Okay, ..." // Problematic field  
      }  
    }  
  ]  
}

Open WebUI ignores reasoning_content, leaving the reasoning steps invisible.

Proposed Fix

Update Open WebUI to parse reasoning_content or map it to the existing content field.

Additional Details

Example API response snippet showing reasoning_content usage:

data: {"choices":[{"delta":{"reasoning_content":"Okay"}}]}  
data: {"choices":[{"delta":{"reasoning_content":","}}]}

Notes for Submitter:

Replace placeholders (e.g., [e.g., Ubuntu 22.04]) with your actual environment details.
Attach logs/screenshots if available.

This version is concise, uses code blocks for clarity, and highlights the core issue. Adjust as needed!

Originally created by @Lesiuk on GitHub (Feb 5, 2025). # Bug Report **Summary**: Open WebUI fails to display Deepseek API's `reasoning_content` due to field mismatch. ## Environment - **Installation Method**: Docker (replace with your method) - **Open WebUI Version**: [e.g., v0.3.11] - **Ollama (if applicable)**: [N/A or version] - **Operating System**: [e.g., Ubuntu 22.04] - **Browser**: [e.g., Chrome 120.0] **Confirmation**: - [x] Read README.md instructions - [x] Latest Open WebUI version - [ ] Browser/Docker logs included (if applicable) ## Expected Behavior - Reasoning content from Deepseek API should appear in Open WebUI within `` <details type="reasoning" done="false"> <summary>Thinking…</summary> > tags (e.g., `Okay, ... </details> `). ## Actual Behavior - Reasoning content is **not displayed** because Deepseek returns it in a `reasoning_content` field instead of populating `content`. ## Reproduction Steps 1. Send a request to Deepseek's API (e.g., via Open WebUI). 2. Observe the API response format: ```json { "choices": [ { "delta": { "reasoning_content": "Okay, ..." // Problematic field } } ] } ``` 3. Open WebUI ignores `reasoning_content`, leaving the reasoning steps invisible. ## Proposed Fix - Update Open WebUI to parse `reasoning_content` **or** map it to the existing `content` field. ## Additional Details - Example API response snippet showing `reasoning_content` usage: ``` data: {"choices":[{"delta":{"reasoning_content":"Okay"}}]} data: {"choices":[{"delta":{"reasoning_content":","}}]} ``` --- **Notes for Submitter**: - Replace placeholders (e.g., `[e.g., Ubuntu 22.04]`) with your actual environment details. - Attach logs/screenshots if available. This version is concise, uses code blocks for clarity, and highlights the core issue. Adjust as needed!

GiteaMirror closed this issue

2025-11-11 15:35:13 -06:00

GiteaMirror commented

2025-11-11 15:35:13 -06:00