microsoft / microsoft/agent-framework
.NET Workflows - Support "inline agents" for declarative workflows
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Object model defines support for invoking an "inline agent": `InvokeAzureResponse`. An "inline agent" effectively specifies the agent definition (instructions, tools, etc) along with the invocation parameters:
```yaml
- kind: InvokeAzureResponse
id: invoke_response_1
conversationId: conv_123xyz
agent:
model:
id: gpt-5
options:
temperature: 0
instructions: Be awesome!
capabilities:
codeInterpeter: true
input:
messages: =UserMessage("Hi!")
arguments:
location: Seattle, WA, USA
now: =System.CurrentDateTime
externalLoop:
variable: Local.UserInput
when: =!Local.IsComplete
maxIterations: 4
output:
autoSend: true
messages: Local.AgentResponse
responseObject: Local.AgentResponseObject
structuredOutputs: Local.AgentStructuredOutputs
```
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 by locating the .NET declarative workflow entry point for InvokeAzureResponse and compare it with the existing object-model support for inline agents. Done means an inline agent can declare its model, instructions, capabilities, invocation inputs, external loop, and outputs using the shown workflow shape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100