Skip to content
Discussion options

You must be logged in to vote

Hi @Expecho, good question. Under the hood both the agent and the service call the same AI model. The difference is in what the abstraction gives you. A ChatCompletionService is a direct call to the model with optional tools or plugins. An Agent, on the other hand, is designed to participate in orchestration. This means you can compose agents into larger workflows, coordinate them with other agents or services, and take advantage of patterns like sequential, concurrent, or handoffs.

If your scenario is just "call an LLM with some tools," then ChatCompletionService is perfectly fine. If you want that call to live inside a broader orchestration story, that’s when the Agent abstraction matters.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Expecho
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
.NET Issue or Pull requests regarding .NET code python Pull requests for the Python Semantic Kernel ai connector Anything related to AI connectors agents
2 participants