logoalt Hacker News

elitoday at 7:43 PM1 replyview on HN

The other "cheating" examples are even worse. It's wild to me that people keep designing benchmarks where the answer is lying around on disk or in the git history. "Hardening" the benchmark with strongly worded prompt instructions is bizarre. There are so many agent sandbox solutions. Why not use one and give it only access to the code it should see?

And I'm not sure how they can rule out other solutions also benefiting from being in the training data, just not reproduced exactly. Seems like it should focus on only CVEs from the last 30 days or something.


Replies

bensyversontoday at 7:56 PM

100%… the fact that they're just using prompting to discourage the agent from looking ahead in the Git history is wild.

show 2 replies