[PR #35] docs: add Thinking Mode and HTTP 400 error troubleshooting for Hermes #158

Open
opened 2026-10-26 09:46:20 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/awesome-deepseek-agent/pull/35
Author: @flowstart
Created: 4/30/2026
Status: 🔄 Open

Base: main ← Head: docs/hermes-thinking-mode-400-error


📝 Commits (1)

  • 8108d2b docs: add thinking mode and 400 error troubleshooting for Hermes

📊 Changes

2 files changed (+118 additions, -0 deletions)

View changed files

📝 docs/hermes.md (+59 -0)
📝 docs/hermes.zh-CN.md (+59 -0)

📄 Description

Summary

Adds a new section to the Hermes integration guide covering DeepSeek's Thinking Mode behavior and its known HTTP 400 error when used with Hermes Agent.

Problem

DeepSeek models have Thinking Mode enabled by default. When Hermes performs tool calls, the model generates reasoning_content (chain-of-thought) that must be passed back in subsequent requests per DeepSeek's API requirement. However, Hermes sets display.show_reasoning to false by default, which strips reasoning_content from the conversation history, causing:

HTTP 400: The `reasoning_content` in the thinking mode must be passed back to the API.

This is a real issue users encounter, and the existing docs don't mention it.

Changes

  • Add section on Thinking Mode behavior with Hermes
  • Document the HTTP 400 error cause
  • Provide two solutions:
    1. Disable Thinking Mode (recommended) — via extra_body.thinking.type: disabled
    2. Keep Thinking Mode — enable show_reasoning: true to preserve reasoning_content
  • Updated both hermes.md (English) and hermes.zh-CN.md (Chinese)

Verification

  • Both files only add new content; no existing content was modified
  • Both English and Chinese versions are consistent

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/awesome-deepseek-agent/pull/35 **Author:** [@flowstart](https://github.com/flowstart) **Created:** 4/30/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/hermes-thinking-mode-400-error` --- ### 📝 Commits (1) - [`8108d2b`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/8108d2b2ad117f288013498e12fbc55d5d624ba3) docs: add thinking mode and 400 error troubleshooting for Hermes ### 📊 Changes **2 files changed** (+118 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/hermes.md` (+59 -0) 📝 `docs/hermes.zh-CN.md` (+59 -0) </details> ### 📄 Description ## Summary Adds a new section to the Hermes integration guide covering DeepSeek's Thinking Mode behavior and its known HTTP 400 error when used with Hermes Agent. ## Problem DeepSeek models have Thinking Mode enabled by default. When Hermes performs tool calls, the model generates `reasoning_content` (chain-of-thought) that must be passed back in subsequent requests per DeepSeek's API requirement. However, Hermes sets `display.show_reasoning` to `false` by default, which strips `reasoning_content` from the conversation history, causing: ``` HTTP 400: The `reasoning_content` in the thinking mode must be passed back to the API. ``` This is a real issue users encounter, and the existing docs don't mention it. ## Changes - Add section on Thinking Mode behavior with Hermes - Document the HTTP 400 error cause - Provide two solutions: 1. **Disable Thinking Mode** (recommended) — via `extra_body.thinking.type: disabled` 2. **Keep Thinking Mode** — enable `show_reasoning: true` to preserve `reasoning_content` - Updated both `hermes.md` (English) and `hermes.zh-CN.md` (Chinese) ## Verification - Both files only add new content; no existing content was modified - Both English and Chinese versions are consistent --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/awesome-deepseek-agent#158
No description provided.