mirror of
https://github.com/microsoft/agent-framework.git
synced 2026-06-16 21:04:09 +08:00
Ben Thomas
907654a489
* Initial working version with tests.
* Updates to validate class data once instead of for each handler method. Also updated Diagnostics Ids to format of MAFGENWF{NUM}
* Formatting and trying to fix generation project pack.
* Another atempt at getting the genrators project to build.
* More attempts to fix generator build and pack.
* Fixing file encodings.
* Initail round of cleanup.
* Trying to fix packing.
* Still trying to fix pipeline pack.
* Remove obsolescence markers, sample updates, and docs from generator branch.
This commit separates the generator core functionality from the
deprecation of ReflectingExecutor. The removed changes will be
re-added in a dependent branch (wf-obsolete-reflector).
๐ค Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Mark ReflectingExecutor and IMessageHandler as obsolete.
This commit deprecates the reflection-based handler discovery approach
in favor of the new [MessageHandler] attribute with source generation.
Changes:
- Add [Obsolete] to ReflectingExecutor<T>, IMessageHandler<T>, IMessageHandler<T,R>
- Add #pragma to suppress warnings in internal reflection code
- Update Concurrent sample to use new [MessageHandler] pattern
- Add Directory.Build.props for samples to include generator
- Add documentation files explaining the migration
๐ค Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Obsoleteing Reflector-based workflow code generation in favor of Source Generators and updating some samples to use new pattern.
This commit deprecates the reflection-based handler discovery approach
in favor of the new [MessageHandler] attribute with source generation.
Changes:
- Add [Obsolete] to ReflectingExecutor<T>, IMessageHandler<T>, IMessageHandler<T,R>
- Add #pragma to suppress warnings in internal reflection code
- Update Concurrent sample to use new [MessageHandler] pattern
- Add Directory.Build.props for samples to include generator
- Add documentation files explaining the migration
๐ค Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Cleaning up temporary design and progress files.
---------
Co-authored-by: alliscode <bentho@microsoft.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Chris <66376200+crickman@users.noreply.github.com>
907654a489
ยท
2026-02-04 20:07:43 +00:00
History
Workflow Getting Started Samples
The getting started with workflow samples demonstrate the fundamental concepts and functionalities of workflows in Agent Framework.
Samples Overview
Foundational Concepts - Start Here
Please begin with the Foundational samples in order. These three samples introduce the core concepts of executors, edges, agents in workflows, streaming, and workflow construction.
The folder name starts with an underscore (
_Foundational) to ensure it appears first in the explorer view.
| Sample | Concepts |
|---|---|
| Executors and Edges | Minimal workflow with basic executors and edges |
| Streaming | Extends workflows with event streaming |
| Agents | Use agents in workflows |
| Agentic Workflow Patterns | Demonstrates common agentic workflow patterns |
| Multi-Service Workflows | Shows using multiple AI services in the same workflow |
| Sub-Workflows | Demonstrates composing workflows hierarchically by embedding workflows as executors |
| Mixed Workflow with Agents and Executors | Shows how to mix agents and executors with adapter pattern for type conversion and protocol handling |
| Writer-Critic Workflow | Demonstrates iterative refinement with quality gates, max iteration safety, multiple message handlers, and conditional routing for feedback loops |
Once completed, please proceed to other samples listed below.
Note that you don't need to follow a strict order after the foundational samples. However, some samples build upon concepts from previous ones, so it's beneficial to be aware of the dependencies.
Agents
| Sample | Concepts |
|---|---|
| Foundry Agents in Workflows | Demonstrates using Azure Foundry Agents within a workflow |
| Custom Agent Executors | Shows how to create a custom agent executor for more complex scenarios |
| Workflow as an Agent | Illustrates how to encapsulate a workflow as an agent |
| Group Chat with Tool Approval | Shows multi-agent group chat with tool approval requests and human-in-the-loop interaction |
Concurrent Execution
| Sample | Concepts |
|---|---|
| Fan-Out and Fan-In | Introduces parallel processing with fan-out and fan-in patterns |
Loop
| Sample | Concepts |
|---|---|
| Looping | Shows how to create a loop within a workflow |
Workflow Shared States
| Sample | Concepts |
|---|---|
| Shared States | Demonstrates shared states between executors for data sharing and coordination |
Conditional Edges
| Sample | Concepts |
|---|---|
| Edge Conditions | Introduces conditional edges for dynamic routing based on executor outputs |
| Switch-Case Routing | Extends conditional edges with switch-case routing for multiple paths |
| Multi-Selection Routing | Demonstrates multi-selection routing where one executor can trigger multiple downstream executors |
These 3 samples build upon each other. It's recommended to explore them in sequence to fully grasp the concepts.
Declarative Workflows
| Sample | Concepts |
|---|---|
| Declarative | Demonstrates execution of declartive workflows. |
Checkpointing
| Sample | Concepts |
|---|---|
| Checkpoint and Resume | Introduces checkpoints for saving and restoring workflow state for time travel purposes |
| Checkpoint and Rehydrate | Demonstrates hydrating a new workflow instance from a saved checkpoint |
| Checkpoint with Human-in-the-Loop | Combines checkpointing with human-in-the-loop interactions |
Human-in-the-Loop
| Sample | Concepts |
|---|---|
| Basic Human-in-the-Loop | Introduces human-in-the-loop interaction using input ports and external requests |