Skip to content

Memory Management and Plugin: MagenticOrchestration #12232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mjnong opened this issue May 22, 2025 · 3 comments
Open

Memory Management and Plugin: MagenticOrchestration #12232

mjnong opened this issue May 22, 2025 · 3 comments
Assignees
Labels

Comments

@mjnong
Copy link

mjnong commented May 22, 2025

Problem

I’m experimenting with the new orchestration APIs in Semantic Kernel and I’ve run into a few limitations:

  1. No history insertion/retrieval
    There doesn’t seem to be any way to insert or fetch conversation history (e.g., by thread or session ID). Is this functionality available, or am I missing something?

  2. No plugin support at the Orchestrator level
    While agents can register plugins (e.g., TimePlugin()), I’d love to be able to attach plugins directly to the Orchestrator so they could be shared across all orchestrations.

  3. No streaming output
    I haven’t found a way to stream generated content back to the caller. Is streaming support on the roadmap?


What I’m looking for

  • Memory / Context management

    • Ability to persist and retrieve arbitrarily-keyed context or history for an orchestration.
  • Plugins inside the Orchestrator

    • A mechanism to register and invoke plugins (e.g., logging, timers, data enrichment) directly on the orchestrator instance.
  • Streaming responses

    • Support for chunked or real-time streaming of content generated by the orchestration.

If any of these are already supported or there are recommended workarounds, I’d appreciate pointers. Otherwise, are there plans to add these capabilities?

Thanks!
— Marcus

@moonbox3
Copy link
Contributor

Thank you for the feedback, @mjnong. Adding @TaoChenOSU.

@moonbox3 moonbox3 removed the triage label May 22, 2025
@mjnong
Copy link
Author

mjnong commented May 23, 2025

I'm also wondering whether or not this is working with AzureAIAgents because I didn't get it to work.

@seizeuniverse
Copy link

I am also interested how to make it work with AzureAIAgents and + history context into this orch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

5 participants