microsoft-agent-framework

Multi-agent orchestration requires importing official classes like ConcurrentBuilder, GroupChatBuilder, and HandoffBuilder. You should instantiate and delegate to these official builders using an adapter pattern rather than writing custom implementations to ensure full interoperability.

Custom agent classes cause runtime errors because they break interoperability with the official Microsoft Agent Framework. You must use official classes like ChatAgent and AgentThread, then run the project's verification script to catch anti-patterns and confirm compliance.

The adapter pattern for builders involves wrapping your custom implementation around official classes like MagenticBuilder or WorkflowExecutor. Your custom builder delegates operations to the official builder, ensuring compatibility while passing CI checks through a verification script.

Building a Magentic-style manager without the official MagenticBuilder is an anti-pattern that causes implementation defects. You must import and delegate to MagenticBuilder directly, then run the backend verification script to confirm correct imports and framework compliance.

You verify correct Microsoft Agent Framework imports by running the project's explicit backend verification script. This script checks for official classes like ChatAgent and WorkflowExecutor, prevents incorrect custom implementations, and ensures your code passes CI checks.

You need WorkflowExecutor for agent handoffs when implementing multi-agent orchestration logic in backend codebases. Import WorkflowExecutor alongside HandoffBuilder, apply the adapter pattern to delegate execution, and run the verification script to ensure safe operations.