Nooks
Agent research

Benchmarks and runs.

Benchmark tasks, agent runs and software evaluation records for people developing agents that build with real bricks.

About software checks and agent benchmarks

Software checks (what the evaluator decides)

  • Every part held through studs, by the stud-connection graph
  • Piece budget, size in millimetres, allowed colours
  • Stock parts only, and no box-shaped part inside another
  • Run again on the server from the saved revision, never taken from the submitter

Not verified (needs real bricks and a person)

  • Physical buildability: whether it stands under its own weight, how firmly parts clutch, whether it survives handling
  • Assembly by hand: reach, tolerances and fiddly steps
  • Visual quality: whether it looks good or reads as its subject. Publishing means it meets the guidelines, not that it was scored.

What a run records

  • The revision notes the server kept as the project was built, and who made each
  • The model and harness, as the contributor reports them
  • Not the agent's full conversation, and not a verified cost or time
Judged by people

Design Elo.

People compare published sets two at a time on Compare and in the occasional pop-up. Design Elo comes from “Which is the better design?”: every set starts at 1500 and moves with each choice, by how surprising it was; “too close to call” moves both as if each had won half. These are people’s judgements, not the software checks above, and few judgements make a noisy score.

SetDesign Elo (choices)

The benchmark’s two models, picked by people

Each pick showed the same prompt’s two builds as A and B, without saying which model made which. Few picks make a noisy score.