PyTorch-style framework trains model-agnostic AI harnesses

The project, hosted at github.com/workofart/harness-training, emerged from several months of development. The core insight is that a harness—a learned wrapper or adapter around a task language model—can be trained once against a specific task environment with a frozen model, then reused across different models and environments without retraining.

The workflow is straightforward: a researcher trains the harness once using a PyTorch-like training framework, and then the trained harness can be evaluated with any task language model on any new task environment. Currently, the framework integrates with any OpenAI-compatible API for the task LLM interface and supports Terminal-Bench and SWE-Bench benchmarks as task environments. However, the architecture is designed to be extensible, allowing users to add support for custom task environments.

The framework provides a familiar PyTorch-style API. Users define a training configuration (via a YAML file), then instantiate a Trainer with an estimator (e.g., AgenticEstimator using a CodexAgentBackend), a criterion (e.g., StrictPareto for multi-objective optimization), and an optimizer (e.g., GreedyMonotonic). Training then proceeds over epochs, yielding loss values as metrics. This design pattern mirrors standard PyTorch training loops, making the framework accessible to developers already familiar with deep-learning frameworks.

The project addresses a practical bottleneck in AI training: the need to retrain or retune models each time a new model or task environment is introduced. By decoupling the harness training from both the task LLM and the task environment, the approach reduces computational waste and enables faster iteration. The researcher framed this as a shift from "agent-driven self-improving harness" to "harness training," emphasizing that the harness itself—not the underlying model—is the primary learnable component.

The PyTorch-like framework design is notable because it lowers the barrier for adoption among ML practitioners familiar with standard deep-learning tooling. The choice to support OpenAI-compatible APIs means developers can experiment with a broad range of models without implementation friction, while the extensible architecture allows researchers to add support for new benchmarks and task environments as needed.

No comments yet. Be the first to share your thoughts!