---
type: email
from: hvppycoding <notifications@github.com>
subject: [openai/openai-agents-python] `reasoning_content` support for models

 other than DeepSeek (GLM, Kimi, etc.) (Issue #2669)
received: 2026-03-15 22:02:53
date_header: Fri, 13 Mar 2026 23:46:41 -0700
priority: normal
status: awaiting_approval
uid: 45625
---

## Email Content

**From:** hvppycoding <notifications@github.com>
**Subject:** [openai/openai-agents-python] `reasoning_content` support for models

 other than DeepSeek (GLM, Kimi, etc.) (Issue #2669)
**Date:** Fri, 13 Mar 2026 23:46:41 -0700

### Body (preview)

hvppycoding created an issue (openai/openai-agents-python#2669)



**Title:**  

`reasoning_content` support for models other than DeepSeek (Kimi, GLM, etc.)



**Body:**



## Problem



When using tool-calling agents with Moonshot AI Kimi models, multi-turn conversations fail with a `400` error on the second turn.



These models include a `reasoning_content` field in their responses. When tool calls are also present, the `reasoning_content` must be included in the assistant message sent back to the API on the next turn — otherwise the API rejects the request.



Currently this behaviour is only implemented for DeepSeek models.



**Affected models:**

- Moonshot AI: `kimi-k2`, `kimi-k2.5`, and other Kimi reasoning variants — `reasoning_content` is **required** for multi-turn tool-calling; omitting it causes a `400` error.

- Zhipu AI: `GLM-5`, etc. — `reasoning_content` is not strictly required (no error without it), but including it is beneficial for model performance.



## Question



Is there a recommended way to support `reasoning_content` for these additional providers?



-- 

Reply to this email directly or view it on GitHub:

https://github.com/openai/openai-agents-python/issues/2669

You are receiving this because you are subscribed to this thread.



Message ID: <openai/openai-agents-python/issues/2669@github.com>

---

## Suggested Actions
- [ ] Reply
- [ ] Archive
- [ ] Escalate
