Replies: 1 comment 4 replies
-
|
Adding @stephentoub for help. |
Beta Was this translation helpful? Give feedback.
4 replies
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a
ChatClientAgentin an API endpoint. A request comes in with a question, an agent is created and returns the answer to the question.In order to keep history and allow follow up questions, I'm serializing and deserializing the
ChatClientAgentThreadfor each request so that the agent has the full history. This works fine.I'm now trying to move to a kind of orchestrator pattorn, using a workflow with handoff instead. This gives me a
WorkflowThread. The problem with that thread is that it can't be serialized (https://github.com/microsoft/agent-framework/blob/9148392d00dafa47a95178622f3800f89bbf0425/dotnet/src/Microsoft.Agents.AI.Workflows/WorkflowThread.cs).Is this by design or just not implemented yet? Are there other more recommended approaches to solve this type of issue (restoring history/context between requests).
It also seems like the
WorkflowThreadonly contains the original question. Not the reply and not any messages of the sub agents. Is something else keeping the full history, or is the idea that each agent should store and restore their own thread history? What's the best approach to pass some kind of thread id to each agent in that case?This is .NET using 1.0.0-preview.251009.1.
Beta Was this translation helpful? Give feedback.
All reactions