* Fix Python pyright package scoping and typing remediation Implements issue #4407 by removing the root pyright include, adding package-level pyright includes, and resolving pyright/mypy typing issues across Python packages. Also cleans unnecessary casts and applies line-level, rule-specific ignores where external libraries are too dynamic. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Reduce pyright cost in handoff cloning Simplify cloned_options construction in HandoffAgentExecutor to avoid expensive TypedDict narrowing/inference in _handoff.py, which was causing pyright to spend a long time in orchestrations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix types * Fix lint and type-check regressions Resolve current Python package check failures across lint, pyright, and mypy after recent code changes, including purview/declarative pyright issues and multiple ruff simplification findings. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fixed hooks * Stabilize package tests and test tasks Resolve cross-package non-integration test failures, simplify streaming type flow, harden locale/culture handling, and standardize package test poe tasks to exclude integration tests where applicable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * lots of small fixes * Fix current Python test regressions Address current failing unit tests in azure-ai, bedrock, and azure-cosmos while keeping Bedrock parsing logic inline (no new static helper methods). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * small fixes * small fixes * removed pydantic from json * final updates * fix core * fix tests * fix obser --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Agent Framework Lab
This is the experimental package for Microsoft Agent Framework, agent-framework-lab, which contains
various lab modules built on top of the core framework.
Lab modules are not part of the core framework and may experience breaking changes or be deprecated in the future.
What are Lab Modules?
Lab modules are extensions to the core Agent Framework that fall into one of the following categories:
- Incubation of new features that may get incorporated by the core framework.
- Research prototypes built on the core framework.
- Benchmarks and experimentation tools.
Lab Modules
- gaia: Evaluate your agents using the GAIA benchmark for general assistant tasks
- tau2: Evaluate your agents using the TAU2 benchmark for customer support tasks
- lightning: RL training for agents using Agent Lightning
Repository Structure
agent-framework-lab/
├── pyproject.toml # Single package configuration for agent-framework-lab
├── README.md # This file
├── LICENSE # License file
├── namespace/ # Centralized namespace package files
│ └── agent_framework/
│ └── lab/
│ ├── gaia/ # Re-exports from agent_framework_lab_gaia
│ ├── lightning/ # Re-exports from agent_framework_lab_lightning
│ └── tau2/ # Re-exports from agent_framework_lab_tau2
├── gaia/ # GAIA module implementation
│ └── agent_framework_lab_gaia/
├── lightning/ # Lightning module implementation
│ └── agent_framework_lab_lightning/
└── tau2/ # TAU2 module implementation
└── agent_framework_lab_tau2/
This structure maintains a single PyPI package agent-framework-lab while supporting modular imports through the namespace package mechanism.
Installation
To install each lab module, use the extras syntax with pip:
pip install "agent-framework-lab[gaia]"
pip install "agent-framework-lab[tau2]"
pip install "agent-framework-lab[lightning]"
Usage
Import and use lab modules from the agent_framework.lab namespace.
For example, to use the GAIA module:
# Using GAIA module
from agent_framework.lab.gaia import GAIA
Should I consume Lab Modules?
If you are looking for stable and production-ready features, you should not use lab modules. Stick to the core framework.
If you are looking for experimentation, research, or want to benchmark different approaches -- most importantly, if you don't mind breaking changes and potential deprecations -- then lab modules are for you.
Contributing to Lab Modules
Microsoft-maintained modules
For Microsoft-maintained modules in this repository, please follow standard contribution guidelines and submit pull requests directly to this repository.
Community modules
If you want to contribute a community-maintained lab module:
- Create a new repository on GitHub for your module
- Tag your repository with
agent-framework-labfor discoverability - Submit a PR to add a link to your repository in the Lab Modules section above
- Use the PR title format:
[New Lab Module] Your Module Name
We will review your submission based on the guidelines below.
Guidelines
- Purpose: Community modules should fit into one of the three categories of lab modules (incubation, research, benchmarks)
- Namespace: Community modules should avoid the
agent_framework.labnamespace (reserved for modules maintained in this repository) - Dependencies: Minimize external dependencies, always include
agent-frameworkas a base dependency - Documentation: Include comprehensive README with installation instructions and usage examples
- Tests: Write comprehensive tests with good coverage
- Type hints: Always include type hints and a
py.typedfile - Versioning: Use semantic versioning, start with
0.1.0for initial releases