.NET runtime interface to match python - add registration to interface and InMemoryRuntime #5207
Assignees
Labels
dotnet
issues related to AutoGen.Net
Comments
3 tasks
3 tasks
MohMaz
pushed a commit
to MohMaz/autogen
that referenced
this issue
Jan 29, 2025
…o interface and inmemoryruntime (microsoft#5215) * add Registry abstractions and Registry Storage to Core/Contracts * brings Grpc in line with these abstractions * add registeragenttype to in memory runtime. Note it's not necessary to call this because we register all the agents with reflection unless you tell the runtime not to..... ## Why are these changes needed? Bringing the .NET more in line with the python ## Related issue number close microsoft#5207 ## Checks - [] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally. - [x ] I've added tests (if relevant) corresponding to the changes introduced in this PR. - [x] I've made sure all auto checks have passed. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What feature would you like to be added?
add RegisterAgentType to the agent runtime (its already in the backend server, but in memory we don't need it because we just load the agents from relection.
Why is this needed?
In .NET when the agents are all in one process we can use reflection to register agents and technically don't need registration. But we desire to match with the python runtime interface so I'm adding it. this may also enable scenarios like the one @colombod has proposed in which the in memory runtime could at some point self-federate into a larger agent system with distributed runtimes.
The text was updated successfully, but these errors were encountered: