microsoft / microsoft/agent-framework
.NET Workflows - Support multiple input messages for declarative workflow invocation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
While the workflow framework is adaptable to any type of input, for declarative workflow (DeclarativeWorkflowExecutor) the root executor contains an embedded assumption that the input can be tranformed into a ChatMessage:
ChatMessage input = inputTransform.Invoke(message);
This logic needs to be updated to support multiple input messages.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at DeclarativeWorkflowExecutor, specifically the inputTransform.Invoke(message) conversion to ChatMessage. Trace the declarative invocation path and determine how completion should be verified when multiple input messages are supplied; the issue names no file or test, so locate the relevant .NET workflow coverage before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100