microsoft / microsoft/agent-framework
.NET Workflows - Support specification of `last_request_id` for `InvokeAzureAgent`
Open
.NET
declarative
workflows
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
When conversation is not specified and external inputs is provided, need to specify `last_request_id` for function result, tool approval, human-in-the-loop input..basically any result provided via a request-port / external-request.
Contributor guide
Research direction
Start at the .NET implementation of InvokeAzureAgent and trace how request-port or external-request results are produced when no conversation is specified. Check the function result, tool approval, and human-in-the-loop input paths; done means each such result can carry the specified last_request_id.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- ai-infra-agents
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100