docs: document `reasoning_content` output removal as a breaking client change (#50624)
Signed-off-by: fede-kamel <fkamelhar@gmail.com> Signed-off-by: Harry Mellor <19981378+hmellor@users.noreply.github.com> Co-authored-by: Harry Mellor <19981378+hmellor@users.noreply.github.com>
Fede Kamelhar committed
Aug 3, 2026 at 09:45 UTC
005fa017566177e1a66d75eba7908d326c5acd60
1 file changed
+2
-1
docs/features/reasoning_outputs.md
+2
-1
@@ -6,6 +6,7 @@ Reasoning models return an additional `reasoning` field in their outputs, which
6
7
!!! warning
8
`reasoning` used to be called `reasoning_content`. To migrate, directly replace `reasoning_content` with `reasoning`.
9
+ It is important that you also update your client code. Otherwise, your client code could silently read an empty `reasoning_content`, even when `reasoning` is populated.
10
11
## Supported Models
12
@@ -105,7 +106,7 @@ Streaming chat completions are also supported for reasoning models. The `reasoni
106
}
107
```
108
108
-OpenAI Python client library does not officially support `reasoning` attribute for streaming output. But the client supports extra attributes in the response. You can use `hasattr` to check if the `reasoning` attribute is present in the response. For example:
109
+OpenAI Python client library does not officially support `reasoning` attribute for streaming output. But the client supports extra attributes in the response. You can use `getattr` to check if the `reasoning` attribute is present in the response. For example:
110
111
??? code
112