Replies: 1 comment 1 reply
-
Hi @rong-xyz, thanks for raising this. We definitely need an update! We are planning development for a new feature that will allow users to opt-in to a standard AIMessage format that catches up with a few recent innovations from major providers (reasoning output, citations, and potentially other items like web search results and code execution blocks). Under this format, [
{
"type": "reasoning",
"reasoning": "...",
"id": "...",
},
{
"type": "text",
"text": "...",
},
] This is not a small undertaking unfortunately because it is a breaking change. So:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Checked
Feature request
I am a User that uses models and langchain across multiple providers and users. Unlike Human, AI, Tool Messages that are well defined and is shared amoing different chat models. It seems to me that the thinking in different models are DIVERGING and this is not good.

Eg: In google
https://github.com/langchain-ai/langchain-google/pull/937/files
And in openai it looks like this
This sort of arbitrary definition is not good for a feature that is increasingly common
Motivation
We need a well defined universal definition and schema on how to deal with thought tokens and process them in the sdk, Eg the google genai can't even take the AI msg with thought token back to itself
Proposal (If applicable)
No response
Beta Was this translation helpful? Give feedback.
All reactions