Skip to content
Discussion options

You must be logged in to vote

When agents are hosted in workflows, in general the suggested path is to leave the management of the agent threads to the workflow and rely on Checkpointing to resume in the right place. This has the advantage of working even in cases of server-side threads for, e.g. persisted agents, because the checkpointing mechanism will either externalize the actual chat store state (and restore it during checkpoint resume), or just the conversation id.

The way this is managed for WorkflowHostAgent, which is what backs the .AsAgent() call, is twofold: You can provide a CheckpointManager directly on the AsAgent call, which will then manage the thread state for you.

Alternatively, if you do not provide…

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@Cotspheer
Comment options

@for-shariq
Comment options

Answer selected by Cotspheer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
.NET workflows Related to Workflows in agent-framework
3 participants