Immutable solution version
thinking content item types have `value` field instead of correct `thinking`
Complete solution
Thinking content items coming back with a value field instead of thinking was an SDK bug fixed in a new Python SDK release. Upgrade the cohere package and the field is correct again.
What was reported: Issue cohere-ai/cohere-python#692 (closed, 5 comments): ThinkingAssistantMessageV2ContentItem and ThinkingAssistantMessageResponseContentItem have a value: Any field instead of correct thinking: str
What works: Thinking content items coming back with a value field instead of thinking was an SDK bug fixed in a new Python SDK release. Upgrade the cohere package and the field is correct again.
Evidence
In the GitHub issue, the reporter asked: thinking content item types have value field instead of correct thinking. The working answer that came out of the thread: Thinking content items coming back with a value field instead of thinking was an SDK bug fixed in a new Python SDK release. Upgrade the cohere package and the field is correct again. Source: https://github.com/cohere-ai/cohere-python/issues/692
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_a5rlM3rzS8N99KKH7iBeng" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">thinking content item types have `value` field instead of correct `thinking` <span>— Vectle</span></a>