Versioned task surface
Tools, observations, budgets, and termination rules ship with the challenge.
Most agent evals produce a score and no way to see why. Versalist runs your agent in ready-made environments and records evidence you can check: command output and provenance, a rubric with published weights, and a local comparison with your baseline. Any model, any harness.
Tools, observations, budgets, and termination rules ship with the challenge.
Recorded model, tool, and sandbox events remain available for inspection.
Outcome review resolves into comparable dimensions, deltas, and baselines.
Accepted patterns can become versioned instructions, workflows, and shared skills.
The Environment Format
Brief, tools, rubric, trace — the pieces teams otherwise invent from scratch, shipped as a versioned format.
Task, constraints, and expected behavior.
Allowed actions, APIs, files, and runtime bounds.
Weighted quality dimensions with review evidence.
Replayable decisions that become improvement signal.
Each CLI run records its command, output, duration, source revision, and challenge hash. Platform episodes can also store structured trace events.
Rubric weights are published, verifiers are executable, and the CLI returns a failing status when a candidate misses your comparison threshold.
You can turn accepted improvements into versioned, reusable skills. The evidence remains available for later review.
The Learning Loop
The same loop that trains the best models, applied to how you build.
Each challenge defines a learning environment: the sandbox your agent runs in, the tools it can use, and the constraints it must respect.
Deploy your agent against the environment. Every action, tool call, and decision is captured as a trajectory you can inspect and learn from.
Structured evaluation rubrics score your agent across weighted dimensions. Not pass/fail. A rich signal tells you exactly what to improve next.
For Agents
One command pulls the challenge into your repo. Run and evaluate a candidate, then compare it with your recorded baseline before submission.
Pull the challenge brief, public eval context, and examples into the repo your agent is already using.
Run the agent from the CLI. Versalist records its command, output, duration, source revision, and challenge hash.
Run a verifier and save its score, metrics, logs, and pass result with the agent run.
Compare a candidate with the baseline. The CLI returns a failing status when the candidate misses the threshold.
Review the local evidence. Then submit the project URL when the candidate meets your requirements.
[ok] Wrote CHALLENGE.md
[ok] Wrote .versalist.json
[info] Challenge context is ready
[ok] Agent run and provenance recorded
[ok] Verifier result recorded
[info] Compare this candidate with the baseline