<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Trial by Trace: Benchmarking AI Agent Harnesses for Reliability and Failure Attribution · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2610.32285/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Wed, 04 Nov 2026 05:35:47 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2610.32285/feed.xml" rel="self" type="application/rss+xml" /><item><title>Trial by Trace: Benchmarking AI Agent Harnesses for Reliability and Failure Attribution — HN submission</title><link>https://news.ycombinator.com/item?id=50337394</link><guid isPermaLink="false">urn:hackerpapers:submission:2610.32285:50337394</guid><pubDate>Mon, 02 Nov 2026 14:35:12 GMT</pubDate><description>&lt;p&gt;Show HN: Nomos – A Go harness that stops coding agents from cheating on tests&lt;/p&gt;&lt;p&gt;Hi HN, Mark here. If you&amp;#x27;ve pointed Claude Code, Cursor, or OpenCode at a codebase you care about and walked away thinking AI coding tools are a net negative, I pretty much agree with you. Left directly on a working branch, models optimize for shutting the compiler up on the current turn. Hit a tricky failure and they delete the failing assertion, return a hardcoded nil/true stub, rewrite the spec to match broken code, dump a 300-line function into the wrong package, or burn $15 of tokens editing in circles. Writing longer rules files (&amp;quot;IMPORTANT: NEVER DELETE TESTS&amp;quot;) breaks down once context…&lt;/p&gt;&lt;p&gt;4 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2610.32285/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.AI</category></item></channel></rss>
