MultiAgentTrainer
Collect data from multiple sources, run autonomous LLM training experiments using autoresearch, and fine-tune open-source or managed models on your corpus. Configure everything in a YAML file and let mat handle ingestion, corpus building, training, and fine-tuning.
MultiAgentTrainer can be used standalone, but is designed as a companion to AgentTester — use AgentTester to evaluate and compare coding agents, then use MultiAgentTrainer to train models on the data those agents produce and consume.
Install
uv pip install -e ".[dev]"
# For open-source fine-tuning (HuggingFace + PEFT/LoRA):
uv pip install -e ".[opensource]"
Quick Start
# List configured data sources
mat sources
# Ingest data sources without training (inspect the corpus)
mat ingest
# Run the full pipeline: ingest → corpus → train
mat train
# Run with overrides
mat train --max-experiments 10 --output-dir ./my-runs
# Label a run so it shows up clearly in mat watch
mat train --name llama3
# Run multiple models in parallel and watch progress live
mat train --config llama3.yaml --name llama3 &
mat train --config mistral.yaml --name mistral &
mat watch
# Check past training runs
mat status
Data Sources
Configure data sources in multiagenttrainer.yaml:
sources:
# Local git repository
- type: local_repo
path: /home/user/my-project
# Any git-cloneable URL
- type: remote_repo
url: "https://github.com/user/repo.git"
branch: main
# GitHub repository (web URL)
- type: github_repo
url: "https://github.com/user/repo"
# All repos in a GitHub organisation
- type: github_org
url: "https://github.com/my-org"
max_repos: 50
visibility: all # all | public | private
# AWS Bedrock knowledge base
- type: bedrock_knowledge_base
knowledge_base_id: "ABCDEF1234"
region: "us-east-1"
query: "training data for code generation"
max_results: 100
Configuration
Copy config.example.yaml to multiagenttrainer.yaml in your working directory.
Top-level sections
| Section | Description |
|---|---|
autoresearch |
Autoresearch repo URL/path, branch, train time, optional program.md override |
sources |
List of data sources to ingest |
training |
Agent command, max experiments, output directory, execution target |
Execution targets
By default experiments run locally. Set training.execution.type to run on a remote host or inside a container instead.
SSH — rsync the workspace to a remote machine and run experiments over SSH:
training:
execution:
type: ssh
ssh_host: user@gpu-box.example.com # required
ssh_key: ~/.ssh/id_ed25519 # optional; uses SSH default otherwise
remote_dir: /tmp/mat-runs # base dir on the remote host
Docker — copy the workspace into a running container and exec commands inside it:
training:
execution:
type: docker
container: my-training-container # required; must already be running
container_dir: /tmp/mat-runs # base dir inside the container
Source Types
| Type | Required Fields | Optional Fields |
|---|---|---|
local_repo |
path |
include, exclude, name |
remote_repo |
url |
branch, name |
github_repo |
url |
branch, name |
github_org |
url |
max_repos, visibility, name |
bedrock_knowledge_base |
knowledge_base_id |
region, query, max_results, name |
Fine-Tuning
Fine-tune models directly on your ingested corpus using mat finetune. Two backends are supported today; more can be added by subclassing FineTuner.
Open-source models (HuggingFace + LoRA/QLoRA)
Requires a local GPU and pip install 'multiagenttrainer[opensource]'.
# multiagenttrainer.yaml
finetuner:
backend: opensource
jobs_dir: ./finetune-jobs
opensource:
model_id: meta-llama/Llama-3.2-1B
output_dir: ./finetuned-models
lora_r: 16
lora_alpha: 32
num_epochs: 3
batch_size: 4
use_4bit: true # QLoRA — requires bitsandbytes + CUDA
# Ingest sources first (or skip if you already have a corpus)
mat ingest
# Fine-tune on the ingested corpus
mat finetune start
# Or point at an arbitrary corpus file
mat finetune start --corpus /path/to/corpus.txt --name my-run
# List all jobs
mat finetune list
# Check a job
mat finetune status <job-id>
Training runs in-process and blocks until complete. The LoRA adapter and tokenizer are saved to output_dir/<job-id>/.
AWS Bedrock model customization
Uses your existing boto3 credentials. Submits a Bedrock customization job and returns immediately — poll with mat finetune status.
finetuner:
backend: bedrock
jobs_dir: ./finetune-jobs
bedrock:
base_model_id: amazon.titan-text-lite-v1
region: us-east-1
role_arn: arn:aws:iam::123456789012:role/BedrockFineTuningRole
output_s3_uri: s3://my-bucket/finetuned-models/
training_data_s3_uri: s3://my-bucket/training-data/
customization_type: CONTINUED_PRE_TRAINING # or FINE_TUNING
epochs: 1
mat finetune start
mat finetune status <job-arn>
mat finetune cancel <job-arn>
Adding a new backend
Subclass FineTuner, implement the four abstract methods, add a config dataclass, and register it in finetuner/registry.py:
# finetuner/finetuner.py
class AnthropicFineTuner(FineTuner):
def prepare_dataset(self, corpus_path): ...
def start_job(self, dataset, job_name): ...
def get_status(self, job_id): ...
def cancel_job(self, job_id): ...
def describe(self): ...
# finetuner/registry.py
if cfg.backend == "anthropic":
return AnthropicFineTuner(cfg.anthropic, jobs_dir, console)
How It Works
- Ingest — Fetch data from all configured sources (clone repos, query Bedrock KBs)
- Build corpus — Walk fetched files, filter by include/exclude globs, concatenate into a single corpus
- Setup — Clone autoresearch, inject the corpus, optionally override
program.md - Train — Launch the agent command iteratively for up to
max_experimentsrounds - Report — Generate a markdown report with experiment results, best
val_bpb, and stats - Fine-tune (optional) — Run
mat finetune startto fine-tune a model on the same corpus
Development
uv pip install -e ".[dev]"
ruff check src/ tests/
ruff format src/ tests/
pytest
Docker
docker compose run --rm mat train
docker compose run --rm mat sources
Library Usage
import asyncio
from pathlib import Path
from multiagenttrainer import Ingester, Runner, load_config
async def main():
cfg = load_config()
ingester = Ingester(cfg.sources, Path(".staging"))
ingester.fetch_all()
ingester.build_corpus(Path("corpus.txt"))
runner = Runner(cfg.autoresearch, cfg.training, name="my-run")
workspace = runner.setup_workspace(Path("corpus.txt"))
results = await runner.run_experiments(workspace)
for r in results:
print(f"experiment {r.experiment_id}: val_bpb={r.val_bpb}")
asyncio.run(main())
Metadata
Release files for multiagenttrainer 2.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| multiagenttrainer-2.0.2.tar.gz | 221.9 kB | With provenance | Details for multiagenttrainer-2.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| multiagenttrainer-2.0.2-py3-none-any.whl | Python 3 | none | any | Details for multiagenttrainer-2.0.2-py3-none-any.whl |
Total release size: 262.3 kB
Release files / multiagenttrainer-2.0.2.tar.gz
| Download URL | multiagenttrainer-2.0.2.tar.gz |
|---|---|
| Size | 221.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
237e83365c29ce21413c42996acac9800cdcf5e31ee259cf46d2656a9c933877
|
|
BLAKE2b-256 checksum How to use checksums |
842b847746472096bd5b62c52d95f5440320042b59e22ac2ebd082c66b203f37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 19, 2026.
Transparency logRelease files / multiagenttrainer-2.0.2-py3-none-any.whl
| Download URL | multiagenttrainer-2.0.2-py3-none-any.whl |
|---|---|
| Size | 40.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
70c8ae50eac45437366a93c127b3f4d69f0c2275fd55b2c04c62137beed4a9f9
|
|
BLAKE2b-256 checksum How to use checksums |
17f954be18b21bd5ae2230d48d5d2a79403ad38d5e565e91c49035616b53775a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 19, 2026.
Transparency logSecurity for multiagenttrainer 2.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for multiagenttrainer-2.0.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.