You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the OpenAiClient.AsIChatClient().AsAIAgent().RunAsync() pipeline.
I may be missing a configuration option, but while inspecting the requests sent to the LLM, I noticed that previous reasoning content is not included in subsequent requests.
As a result, after each tool call the agent appears to restart its reasoning process from scratch instead of continuing from the previous reasoning context. This breaks agent loops that rely on maintaining a continuous thought process across tool calls.
Is there currently an option to preserve and forward reasoning content automatically through the agent pipeline?
If not, could this be supported by default? Ideally, the framework should handle TextReasoningContent correctly when constructing the next model request, rather than requiring users to manually convert reasoning content into generic TextContent and inject it back into history.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I am using the OpenAiClient.AsIChatClient().AsAIAgent().RunAsync() pipeline.
I may be missing a configuration option, but while inspecting the requests sent to the LLM, I noticed that previous reasoning content is not included in subsequent requests.
As a result, after each tool call the agent appears to restart its reasoning process from scratch instead of continuing from the previous reasoning context. This breaks agent loops that rely on maintaining a continuous thought process across tool calls.
Is there currently an option to preserve and forward reasoning content automatically through the agent pipeline?
If not, could this be supported by default? Ideally, the framework should handle TextReasoningContent correctly when constructing the next model request, rather than requiring users to manually convert reasoning content into generic TextContent and inject it back into history.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions