Ranked by score, best first. Every title opens the source in a new tab.
Generated scored by claude-haiku-5-5, takes by claude-opus-5-5RSS
Score 8.0 out of 10
Joel Niklaus burned $4,746 of inference and ran 28,849 trials this week to answer one question: which coding agent… (opens in a new tab)
Worth reading. Same model, nine harnesses, 28,849 trials isolates the harness as the variable. Law 3 measured. Check the variance across runs before trusting rankings.
why 8.0
Measured comparison of nine coding agent harnesses on the same model; directly on-topic.
relevance 8/10 · novelty 8/10
Score 6.0 out of 10
Claude Code sends your email address to websites (opens in a new tab)
Real exposure report, but it is one GitHub issue with no snippet. Read it for what the fetch tool sends outbound, not for a confirmed root cause.
why 6.0
Claude Code leaking user email to websites is a concrete permission and data-exposure failure in the harness.
relevance 6/10 · novelty 6/10
Score 6.0 out of 10
Show HN: Stroq – a local audit of what your coding agent did and why (opens in a new tab)
Local audit log of agent actions and stated reasons. Useful if it records effects, not just narration; an agent explaining itself is not an independent check.
why 6.0
Local audit log of what a coding agent did and why; tool-call tracing is a visible harness feature.
relevance 6/10 · novelty 6/10
Score 6.0 out of 10
Inside GitHub’s new Git storage architecture (opens in a new tab)
Infrastructure, not harness. 5,000 concurrent agents and 7,200 pushes per second are internal vendor tests. Relevant only if you run agent swarms against one repo.
why 6.0
GitHub Git storage design targeting thousands of concurrent agents; infrastructure detail with a measured load claim.
relevance 6/10 · novelty 6/10
Score 6.0 out of 10
EPISTEME: Trustworthy Coding Agents Through Tool Call Intent (opens in a new tab)
Solid idea: harness forces declared intent per tool call, then compares it to recorded effects. The effect record is the independent part; the declaration is not. Law 4.
why 6.0
Harness records and checks declared intent against tool-call effects; a concrete permission and audit mechanism.
relevance 6/10 · novelty 6/10
Nothing of this kind on this day.