Workflow orchestration for Inspect AI that enables you to define, run, and manage evaluations at scale — from configuration through to production.
As evaluation workflows grow in complexity—running multiple tasks across different models with varying parameters, then reviewing, validating, and promoting results—managing these experiments becomes challenging. Inspect Flow addresses this by providing:
- Declarative Configuration: Define complex evaluations with tasks, models, and parameters in type-safe schemas
- Repeatable & Shareable: Encapsulated definitions of tasks, models, configurations, and Python dependencies ensure experiments can be reliably repeated and shared
- Powerful Defaults: Define defaults once and reuse them everywhere with automatic inheritance
- Parameter Sweeping: Matrix patterns for systematic exploration across tasks, models, and hyperparameters
- Post-Evaluation Workflows: Tag, validate, and promote evaluation logs with composable steps
Inspect Flow is designed for researchers and engineers running systematic AI evaluations who need to scale beyond ad-hoc scripts.
Before using Inspect Flow, you should:
- Have familiarity with Inspect AI
- Have an existing Inspect evaluation or use one from inspect-evals
pip install inspect-flowOptionally install the Inspect AI VS Code Extension which includes features for viewing evaluation log files.
FlowSpec is the main entrypoint for defining evaluation runs. At its core, it takes a list of tasks to run. Here's a simple example that runs two evaluations:
from inspect_flow import FlowSpec, FlowTask
FlowSpec(
log_dir="logs",
tasks=[
FlowTask(
name="inspect_evals/gpqa_diamond",
model="openai/gpt-4o",
),
FlowTask(
name="inspect_evals/mmlu_0_shot",
model="openai/gpt-4o",
),
],
)To run the evaluations, run the following command in your shell. This will create a virtual environment for this spec run and install the dependencies. Note that task and model dependencies (like the inspect-evals and openai Python packages) are inferred and installed automatically.
flow run config.pyThis will run both tasks and display progress in your terminal.
You can run evaluations from Python instead of the command line.
from inspect_flow import FlowSpec, FlowTask
from inspect_flow.api import run
spec = FlowSpec(
log_dir="logs",
tasks=[
FlowTask(
name="inspect_evals/gpqa_diamond",
model="openai/gpt-4o",
),
FlowTask(
name="inspect_evals/mmlu_0_shot",
model="openai/gpt-4o",
),
],
)
run(spec=spec)Often you'll want to evaluate multiple tasks across multiple models. Rather than manually defining every combination, use tasks_matrix to generate all task-model pairs:
from inspect_flow import FlowSpec, tasks_matrix
FlowSpec(
log_dir="logs",
tasks=tasks_matrix(
task=[
"inspect_evals/gpqa_diamond",
"inspect_evals/mmlu_0_shot",
],
model=[
"openai/gpt-5",
"openai/gpt-5-mini",
],
),
)To preview the expanded config before running it, you can run the following command in your shell to ensure the generated config is the one that you intend to run.
flow config matrix.pyThis command outputs the expanded configuration showing all 4 task-model combinations (2 tasks × 2 models).
log_dir: logs
dependencies:
- inspect-evals
tasks:
- name: inspect_evals/gpqa_diamond
model:
name: openai/gpt-5
- name: inspect_evals/gpqa_diamond
model:
name: openai/gpt-5-mini
- name: inspect_evals/mmlu_0_shot
model:
name: openai/gpt-5
- name: inspect_evals/mmlu_0_shot
model:
name: openai/gpt-5-miniFlow provides additional matrix functions (models_matrix, configs_matrix) for sweeping over model settings, generation configs, and more. See Matrixing for details.
Before running evaluations, preview what would run with --dry-run:
flow run matrix.py --dry-runThis performs the full setup process—importing tasks from the registry, applying all defaults, expanding all matrix functions, and checking for existing logs—showing exactly what would run, but stops before actually running the evaluations.
To run the config:
flow run matrix.pyWhen complete, you'll find a link to the logs at the bottom of the task results summary.
To view logs interactively, run:
inspect view --log-dir logsOnce evaluations complete, use steps to operate on the resulting logs. For example, tag logs after reviewing them:
flow step tag logs/ --add reviewed --reason "Manually inspected"Use flow check to verify the completeness of a spec against a log directory — for example, checking how much of a production directory has been filled:
flow check matrix.py --log-dir s3://bucket/prod/logsSteps can be composed into full workflows — filtering, tagging, and copying logs between directories. See Steps for custom steps, filters, and an end-to-end example.
See the following articles to learn more about using Flow:
- Spec: Flow type system, config structure and basics.
- Defaults: Define defaults once and reuse them everywhere with automatic inheritance.
- Matrixing: Systematic parameter exploration with matrix and with functions.
- Steps: Post-evaluation workflows — tag, validate, and promote logs with composable steps.
- Reference: Detailed documentation on the Flow Python API and CLI commands.
To work on development of Inspect Flow, clone the repository and install with the -e flag and [dev, doc] optional dependencies:
git clone https://github.com/meridianlabs-ai/inspect_flow
cd inspect_flow
uv sync
source .venv/bin/activateOptionally install pre-commit hooks via
make hooksRun linting, formatting, and tests via
make check
make test

