Prime Intellect lança o Verifiers v1: conjuntos de tarefas, arcabouços e ambientes de execução componíveis para treinamento e avaliação de RL agêntico
A Prime Intellect lançou o verifiers 0.2.0, oferecendo uma prévia de um núcleo "v1" reescrito sob o namespace verifiers.v1. Ele divide um ambiente em um conjunto de tarefas (o quê), um arcabouço (o como) e um ambiente de execução (o onde), com um servidor de interceptação que atua como proxy das requisições e registra rastros prontos para treinamento. Qualquer conjunto de tarefas roda sob qualquer arcabouço compatível, com suporte total ao treinamento com prime-rl já no lançamento. O post Prime Intellect lança o Verifiers v1: conjuntos de tarefas, arcabouços e ambientes de execução componíveis para treinamento e avaliação de RL agêntico...
Prime Intellect launched verifiers 0.2.0. It previews a rewritten core, shipped under the new verifiers.v1 namespace. Modern evaluations now run coding agents with tools, compaction, and subagents. Accordingly, v1 rebuilds environments to run these agentic workloads at scale.
What is verifiers v1?
First, consider what verifiers is: Prime Intellect’s environment stack for agentic reinforcement learning and evaluations. Previously, an environment bundled its data, agent logic, and infrastructure together. In contrast, v1 breaks that bundle into three composable pieces.
A taskset defines the work: the data, tools, and scoring. A harness solves the task and produces a rollout. That harness can be a ReAct loop, a CLI agent, or your own. The rollout then runs inside a runtime, either local or in a sandbox. Because the pieces decouple, any taskset runs under any compatible harness.
How the Architecture Works?
With those pieces defined, the next question is how they communicate. The central piece is the verifiers-managed interception server. It sits between the agent’s runtime and the inference server. Specifically, it proxies requests to, and responses from, inference. Meanwhile, it records the trace, sets sampling parameters, and can rewrite tool responses. That rewriting helps mitigate reward hacks during training.
For scale, each server multiplexes a constant number of rollouts, defaulting to 32. A pool then scales elastically with observed concurrency. The server also owns a client that relays those requests. During evaluation, an EvalClient acts as a blind HTTP proxy. During training, a TrainClient wraps renderers for faithful token-in RL training.
Because harnesses speak different dialects, verifiers supports three as of now. These are OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages. A dialect adapter normalizes each wire format into canonical vf.types. Consequently, your scoring logic stays independent of the agent tested.
Run rollout
Harness dialect:
RUNTIME · where (subprocess · Docker · sandbox)
Trace · message graph (v1)
Trace size: v0 vs v1
v0 · quadratic
v1 · linear