Environment Hub
The Environment Hub is Prime Intellect’s collection of user-created tasksets which are installable and ready to use with verifiers.Taskset
A taskset is the collection and loader for the work to evaluate or train on. Each task combines a serializableTaskData row (prompt, files, references, resource requirements) with its task class’s behavior (lifecycle hooks, tools, metrics, and rewards). The taskset’s load() method constructs those objects and declares their task/config types through Taskset[TaskT, ConfigT].
Harness
A harness is the program the model is run in, e.g. Claude Code, Codex or mini-swe-agent.Agent
AnAgent is a reusable (harness × model × runtime policy) value with one executable arrow — agent.run(task) -> Trace — the building block environments hand to run(), and a scripting surface of its own (see Agent).
Environment
The control flow between agents: how many run on one task, in what order, judged how across the finished set. The default is the single-agent case;--env.id pairs a reusable interaction (best-of-n, a judge) with any taskset. One episode yields flat, self-contained traces — each stamped with its episode and agent — persisted whole (one episode per traces.jsonl line).
Toolset
A set of tools defined by the taskset that are installed as MCP servers into the harnesses that support them.Trace
A trace records the message graph, rewards, metrics, errors, and one per-call record (ModelCall) per provider exchange (its model, sampling, finish reason, usage, timing, and any error), etc. When using verifiers for training with prime-rl, it stores additional information such as tokens and logprobs, built incrementally using renderers.
Documentation
- Getting started - How to install verifiers and the needed skills.
- Architecture — How verifiers works behind-the-scenes
- Tasksets — How to create tasksets
- Harbor Tasksets — How to create Harbor-based tasksets
- Evaluation — How to evaluate tasksets
- Harnesses — How to build custom harnesses
- Agent — How to run standalone agents
- Env — How to build multi-agent environments