Repository navigation
.NET: Passing ChatClientAgent specific run options #521
Description
Today we have multiple approaches to passing ChatClientAgent specific run options:
RunAsync, which takesAgentRunOptions? optionsas input, can be passed aChatClientAgentRunOptions- We have a
RunAsyncoverload inChatClientAgentExtensionswhich takesAgentRunOptions? agentRunOptionsandChatOptions? chatOptionsas input.- Since
ChatClientAgentRunOptionsis a subclass ofAgentRunOptions, it can in theory be passed to this overload.ChatClientAgentRunOptionscontains a ChatOptions inside of it, so it's unclear what would happen if someone passed bothChatClientAgentRunOptionsandChatOptions.
- Since
Since the 2nd method has some ambiguity, I propose that we remove it and only keep the original RunAsync method.
Reacted by Roger Barreto and Mark Wallace
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]Passing ChatClientAgent specific run options[/-][+].NET: Passing ChatClientAgent specific run options[/+]rogerbarreto commentedon Aug 28, 2025
Alternatively
AgentRunOptionsexpect the specialization directlyChatClientAgentRunOptionsSome extra thoughts.
How about internalize the
ChatClientAgentRunOptionscompletely, so we avoid adding this ambiguity in the apis and resort to something like:ChatClientAgentRunOptions agentOptions.WithChatOptions(ChatOptions)