* python: replace pre-commit with prek, add PEP 723 script deps, clean up dev dependencies - Replace pre-commit with prek (Rust-native, faster pre-commit alternative) - Move supported hooks to repo: builtin for zero-clone speed - Add new builtin hooks: trailing-whitespace, check-merge-conflict, detect-private-key, check-added-large-files - Update all hook versions to latest (pre-commit-hooks v6, pyupgrade v3.21.2, bandit 1.9.3, uv-pre-commit 0.10.0) - Add PEP 723 inline script metadata to 34 samples with external deps - Remove autogen-agentchat/autogen-ext from dev deps (now declared per-sample) - Remove unused dev deps: pytest-env, tomli-w - Add agent-framework-core>=1.0.0b260130 lower bound to all 21 packages - Update CI workflow to use j178/prek-action - Update docs: DEV_SETUP.md, AGENTS.md, CODING_STANDARD.md, SAMPLE_GUIDELINES.md * updated lock * python: fix prek config paths for local execution and CI workflow Remove global 'files: ^python/' filter and strip python/ prefix from all path patterns in .pre-commit-config.yaml so prek finds files when run from the python/ directory. Update CI workflow to use --cd python instead of --config path. Include trailing whitespace fixes and dev dependency cleanup. * python: move helper scripts to scripts/ folder and exclude from checks * python: exclude AGENTS.md from prek markdown code lint * python: exclude AGENTS.md and azure_ai_search sample from markdown lint * fix m365 sample * python: ignore CPY rule for samples with PEP 723 headers * fix in dev_setup * python: replace aiofiles with regular open in samples * python: suppress reportUnusedImport in markdown code block checker * python: use samples pyright config for markdown code block checker Write a temp pyrightconfig.json matching pyrightconfig.samples.json rules (typeCheckingMode=off, only reportMissingImports and reportAttributeAccessIssue). Filter output to only fail on these rules since syntax-level errors (top-level await, undefined vars) are expected in README documentation snippets. * python: use markdown-code-lint with fixed globs instead of prek file list The prek-markdown-code-lint task received all changed files including non-README markdown and files with pre-existing broken imports. Replace with the standard markdown-code-lint task which uses the correct glob patterns (README.md, packages/**/README.md, samples/**/*.md). * python: exclude READMEs with pre-existing broken imports from markdown lint * python: fix broken README code snippets instead of excluding them - ag-ui: replace TextContent (removed) with content.type == 'text' - durabletask: fix import path to durabletask.worker.TaskHubGrpcWorker - orchestrations: use constructor params instead of .participants() method - observability: mark deprecated code blocks as plain text, filter reportMissingImports to agent_framework modules only - remove README excludes from markdown-code-lint task * add revision to gaia download * feat(python): parallelize checks across packages Run (package × task) cross-product in parallel using ThreadPoolExecutor and subprocesses. Key changes: - Add scripts/task_runner.py with shared parallel execution engine - Update run_tasks_in_packages_if_exists.py to accept multiple tasks - Update run_tasks_in_changed_packages.py with --files flag and parallel support - Add check-packages poe task (fmt+lint+pyright+mypy in parallel) - Add prek-markdown-code-lint and prek-samples-check with change detection - Split CI code quality workflow into parallel prek and mypy jobs - Update DEV_SETUP.md to document new parallel behavior Core package changes still trigger checks on all packages. * feat(ci): split code quality into 4 parallel jobs Split the single prek job into parallel jobs: - pre-commit-hooks: lightweight hooks (SKIP=poe-check) - package-checks: fmt/lint/pyright/mypy via check-packages - samples-markdown: samples-lint, samples-syntax, markdown-code-lint - mypy: change-detected mypy checks All 4 jobs run concurrently (×2 Python versions = 8 runners). * feat(ci): use only Python 3.10 for code quality checks * refactor(python): add future annotations and remove quoted types Add `from __future__ import annotations` to 93 package files that used quoted string annotations, then run pyupgrade --py310-plus to remove the now-unnecessary quotes. Fixes https://github.com/microsoft/agent-framework/issues/3578
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