Recommended Architecture for Context-Persistent AI Assistant #1923
Unanswered
vladbuinceanu
asked this question in
Q&A
Replies: 0 comments
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.
-
Hi everyone,
I’m integrating an AI chat assistant into an ERP platform and I could use some guidance on project structure.
Assistant goals:
I tried different examples and orchestrations patterns and while testing workflows and the handoff pattern, I noticed that each message creates a new workflow instance, causing follow-up inputs to route back to the root agent instead of resuming the last active one. I suspect a state management or human-in-the-loop layer is needed, but i don't know if this is the right approach and I don't want to start in the wrong direction.
I also found this orchestration pattern but the docs seem incomplete for now:
https://learn.microsoft.com/en-us/agent-framework/user-guide/workflows/orchestrations/magentic?pivots=programming-language-csharp
My questions are:
What’s the recommended architecture for this type of system ?
What are best practices for persisting conversation state and task data ?
Any examples, design patterns, or references would be greatly appreciated. Thanks !
Beta Was this translation helpful? Give feedback.
All reactions