The check that caught what the agent's renders missed

If your agent checks its own work by looking at a screenshot and reading the tool's status line, a recent CAD experiment by ModelRift is worth 3 minutes of your time. ModelRift gave six agents the same three printable parts, three in CadQuery and three in OpenSCAD, one agent per cell, unattended, capped at twelve versions, and then checked every exported mesh with a parser that took neither tool's word.

All six parts came out printable. The clearest case on the way there was a threaded adapter whose core cylinder a boolean union silently dropped. The agent read four renders and saw a finished thread. The kernel reported valid=True, solids=1. A volume of 7,065 mm³ against an expected 10,323 caught it. That was one of sixteen failures across the six runs. Nine of them the tool never mentioned, and the renders caught only the coarse ones, like four mounting posts deleted by a cavity subtraction. Every defect that would have ruined a print was found by a number.

Loosening a tolerance produced a negative-volume solid that also reported valid. The other tool certified an export as error-free while it carried four non-manifold edges and sixty zero-area triangles.

This is really a coding-agent problem, just with a 3D mesh instead of code. An agent gets its feedback as a picture, as the tool's verdict, or as a number produced by something that did not build the artifact. A picture checks what a picture can carry, and the agent picks the picture. The tool's verdict is the maker grading its own work. The number from outside was the one that failed the broken part.

The fix? Require agents to pass strict numeric checks before calling a model done: wall thickness, clearances, interference, and a mesh audit that does not ask the tool whether it did a good job. If the only checks in your loop are a picture and a status line, six runs say which defects you will catch.