Skip to content

Persist default DaprChatClient component in Agent Registry #336

@bibryam

Description

@bibryam

When creating an agent without explicitly configuring an LLM chat client, the agent correctly falls back to the default component at runtime. However, the agent registry does not persist which LLM client was selected implicitly.

"llm": {
"api": "chat",
"client": "DaprChatClient",
"model": "unknown",
"prompt_template": "ChatPromptTemplate",
"provider": "dapr"
}

When I specify a concrete component (such as this llm = DaprChatClient(component_name="llm-provider"), it is recorded in the registry as this:

"llm": {
  "api": "chat",
  "client": "DaprChatClient",
  "component_name": "llm-provider",
  "model": "unknown",
  "prompt_template": "ChatPromptTemplate",
  "provider": "dapr"
},

The registry should always record the effective LLM client used by the agent, even when the value comes from a default.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions