HyperHerd
⚠️ Pre-release / actively developed. HyperHerd is in soft launch — the YAML schema, CLI flags, and Python API may change without notice between versions. Pin to an exact version (
hyperherd==X.Y.Z) if you build on top of it, and expect breaking changes until a tagged 1.0.
Hyperparameter sweeps on SLURM, run by an autonomous agent. Declare your search in YAML, hand over a one-line launcher script, and walk away — herd monitor submits trials in stages, diagnoses failures, retries the ones SLURM can fix, and pings you on Discord only when it can't.
📖 Full documentation: allenwlynch.github.io/hyperherd
What you get
- One-command sweeps. Write a YAML, run
herd run, and that's it — no sbatch boilerplate, no manual resubmits. - An agent that operates the sweep for you.
herd monitorramps trials in stages, diagnoses failures, bumps memory or wall-time when that's the right fix, and only interrupts you when it isn't. - Two-way Discord control. A dedicated channel per sweep with deterministic slash commands (
/status,/run,/cancel,/tail, …) and free-form mentions for the agent. - Resume from anywhere. Pull the plug, edit the sweep, re-run — completed trials stick, failed ones go back to the queue.
- Edit mid-run. Bump a learning-rate range or add a value; the next
herd runappends the new trials without disturbing the ones already running. - Configs you don't have to memorize. A bundled Claude Code skill writes
hyperherd.yamlfor you from a one-paragraph description.
Hydra is the recommended trainer harness (its CLI consumes the override format natively), but the launcher is free-form bash — parse the arguments however you want.
Quick start
# Install (Python 3.8+ for the base CLI)
pip install hyperherd
# Install the Claude Code skill for authoring sweep configs
herd install-skill
# Scaffold a workspace
herd init my_experiment
# Edit my_experiment/hyperherd.yaml and my_experiment/launch.sh, then:
herd run my_experiment --dry-run # preview
herd run my_experiment # submit
herd status my_experiment # one-shot status
To run the autonomous monitor (Python ≥ 3.10 + a Discord bot — see Discord setup):
pip install 'hyperherd[monitor]'
herd monitor my_experiment
Have Claude Code set you up
Open Claude Code in your project directory and paste this — it'll walk you through install, config authoring, validation, and (if you want it) the autonomous monitor end-to-end:
Help me set up HyperHerd. Read the setup guide at
https://raw.githubusercontent.com/AllenWLynch/hyperherd/main/docs/setup-help.md
and follow it — start with the Phase 0 interview, then drive the rest.
The full guide is also browsable at allenwlynch.github.io/hyperherd/setup-help.
Documentation
- Getting started — install, scaffold, run your first sweep
- Autonomous monitor — the agent daemon: setup, Discord control, failure triage
- Discord setup — one-time bot creation walkthrough
- Sweep config reference — every field in
hyperherd.yaml - Conditions — filter or modify parameter combinations
- Launcher script — contract + examples (Apptainer, conda, non-Hydra)
- Command reference — every
herdsubcommand - Claude Code skill — authoring configs by asking Claude
Requirements
- Python ≥ 3.8 for the base
herdCLI - Python ≥ 3.10 for the
[monitor]extras (the autonomous monitor — Discord, Claude Agent SDK) - A SLURM cluster with
sbatch,sacct,squeue,scancelon the submission host
Metadata
Release files for hyperherd 0.1.3
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 | |
|---|---|---|---|---|
| hyperherd-0.1.3.tar.gz | 682.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hyperherd-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 833.9 kB
Release files / hyperherd-0.1.3.tar.gz
| Download URL | hyperherd-0.1.3.tar.gz |
|---|---|
| Size | 682.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aceee1516d8c684f44dc52438418b43bc00e3e21446210a8fb3377de48eebb8a
|
|
BLAKE2b-256 checksum How to use checksums |
4c27de5707d4d037f0edbcdd3479e24ca376fbd76ef25c747b464f5413bea58f
|
| 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 21, 2026.
Transparency logRelease files / hyperherd-0.1.3-py3-none-any.whl
| Download URL | hyperherd-0.1.3-py3-none-any.whl |
|---|---|
| Size | 151.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
910bb333c0f1e70b692676e517e49342c64e5becc1f54b2fa6e1cf0c9dcb6ed7
|
|
BLAKE2b-256 checksum How to use checksums |
3ded6a175c131011139925a4ed833d5808b3c948abb874a176a0e4b9a10d1ae5
|
| 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 21, 2026.
Transparency logSecurity for hyperherd 0.1.3
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 hyperherd-0.1.3.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 21, 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.