* chore(python): improve dependency range automation - tighten dependency bounds and coding standards guidance\n- add dependency range validation workflow, reporting, and issue automation\n- update related tests and dependency pins for compatibility Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * updated text and pyarrow * new lock * fixed workflow * updated deps * fix tiktoken * chore(python): refine dependency validation workflows Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * docs(python): add high-level dependency validation comments Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * WIP * added additional comments and excludes * added dev dependency handling and workflow and updates to package ranges * added readme and simplified commands * fix markers * chore(python): address dependency review feedback Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Tighten dependency bounds, remove stale overrides, restore Python 3.10 support - Apply dependency bound policy across all packages: stable >=1.0 deps use >=floor,<next_major; pre-1.0/prerelease deps use validated hard-bounded ranges - Remove stale root tool.uv.override-dependencies (uvicorn, websockets, grpcio) - Lower github_copilot requires-python to >=3.10 with github-copilot-sdk gated behind python_version >= 3.11 marker; import raises ImportError on 3.10 - Skip github_copilot pyright/mypy/test tasks on Python <3.11 - Use version-conditional pyrightconfig for samples on Python 3.10 - Add compatibility fix in core responses client for older openai typed dicts - Normalize uv.lock prerelease mode and refresh dev dependencies - Update CODING_STANDARD.md, DEV_SETUP.md, and package management skill docs Closes #902 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * small tweaks * add note in workflow * fix workflows and several versions * fix duplicate --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
4.6 KiB
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
Running Tests Locally
For machine-safe local runs, prefer package-scoped commands first:
uv run --directory packages/lab poe test
uv run --directory packages/lab pytest -q -m "not integration"
When you need to run package tasks from the repository root, use sequential mode to avoid launching all package tests in parallel:
uv run poe test --seq
Lightning observability tests intentionally exercise heavier tracing paths and are marked as resource_intensive:
uv run --directory packages/lab pytest lightning/tests/test_lightning.py -m "resource_intensive" -q
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