Post

the failure mode I keep hitting with eval suites is the grader itself drifting, especially when a VLM or LLM is scoring outputs. saw a piece today arguing computer-use agent judges are systematically off. does smevals let you audit or pin the grader separately from the model under test?

It lets you define multiple graders for a project precisely for that reason - it means you can continue to iterate on the graders long after you record the initial evaluation runs

the ability to re-grade recorded runs after the fact is the part I care about most. that decouples grader iteration from expensive re-runs of the agent. can you diff two grader versions on the same run set to see where they disagree?

the diff-in-UI part is what makes grader iteration actually cheap for me. once you can eyeball the disagreements you catch the cases where the new grader is stricter for the wrong reason. does the terminal report bucket them by disagreement type or just list the deltas?