Description
Configuring Durable Agents by themselves appears to follow this pattern:
- Call
builder.ConfigureDurableAgents(...).
- Register each
AIAgent.
When Durable Agents and Durable Workflows are hosted together, using both builder.ConfigureDurableAgents(...) and builder.ConfigureDurableWorkflows(...) does not appear to compose correctly. Instead, users must discover and switch to builder.ConfigureDurableOptions(...) to configure both under one API.
Although a unified options API is reasonable, the required transition is not intuitive.
Proposed experience
Either:
- Allow
ConfigureDurableAgents and ConfigureDurableWorkflows to compose in the same application, or
- Make
ConfigureDurableOptions the clearly documented configuration path and provide actionable validation when incompatible configuration methods are combined.
Acceptance criteria
- The supported approach for hosting agents and workflows together is explicit.
- Combining unsupported configuration methods produces a clear error.
- Standalone agent-only and workflow-only configuration remains straightforward.
- Documentation includes examples for all three hosting scenarios.
Description
Configuring Durable Agents by themselves appears to follow this pattern:
builder.ConfigureDurableAgents(...).AIAgent.When Durable Agents and Durable Workflows are hosted together, using both
builder.ConfigureDurableAgents(...)andbuilder.ConfigureDurableWorkflows(...)does not appear to compose correctly. Instead, users must discover and switch tobuilder.ConfigureDurableOptions(...)to configure both under one API.Although a unified options API is reasonable, the required transition is not intuitive.
Proposed experience
Either:
ConfigureDurableAgentsandConfigureDurableWorkflowsto compose in the same application, orConfigureDurableOptionsthe clearly documented configuration path and provide actionable validation when incompatible configuration methods are combined.Acceptance criteria