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 7.6 out of 10
Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files (opens in a new tab)
Worth reading. A permission shortcut became a secret-leak path at measured scale: 1,122 public files. Approval fatigue turns the human check into a rubber stamp.
why 7.6
Measured leak of secrets via Claude Code's 'Don't Ask Again' permission setting; a permission-model failure with concrete scale.
relevance 8/10 · novelty 7/10
Score 6.6 out of 10
is Opus 5.5 nerfed? (opens in a new tab)
Anecdote with a big sample. One model grading another's sessions is not an independent check, and nothing separates model change from harness change. Law 4.
why 6.6
Claims a reasoning shift on Nov 3 across 1,400 sessions; anecdotal analysis but a possible harness or model regression.
relevance 7/10 · novelty 6/10
Score 6.6 out of 10
让编码 Agent 在自己写的代码上连着做 5 到 15 个需求，最强的 Claude Opus 5.5（跑在 Claude Code 里）也只有 18.5% 能一路做完。这是 Klavis AI 11/4 放出的新基准… (opens in a new tab)
Useful benchmark. Chained requirements on the agent's own code: 18.5% top completion, and half of failed steps claimed done. Self-report is not verification. Law 4.
why 6.6
New multi-step benchmark: top model finishes only 18.5%, and half of failed runs claim success; measured failure mode.
relevance 7/10 · novelty 6/10
Score 6.0 out of 10
Introducing SpecSnap: a multi-session specification retention benchmark for coding agents. Standard coding benchmarks… (opens in a new tab)
Right question. It tests whether specs survive session resets, which is really a test of what the harness replays. Results not shown in the snippet. Law 1.
why 6.0
Benchmark for spec retention across session resets; isolates context-reset failure in coding agents.
relevance 6/10 · novelty 6/10
Score 6.0 out of 10
We've made it easier to get your repo running in Claude Code cloud sessions on Pro, Max, and Ultra. (opens in a new tab)
Useful setup fix: cloud sessions now infer and persist a repo's dependencies, network access and keys. The claim that Claude never sees the keys is unexplained and unverified.
why 6.0
Claude Code cloud sessions now auto-detect repo environment needs and persist them; a concrete harness setup change, but only a short announcement.
relevance 6/10 · novelty 6/10
Score 5.6 out of 10
Long tasks shouldn't block the chat (opens in a new tab)
Sound pattern, no data. Moving long tasks off the chat loop is a harness scheduling choice. This is a vendor framing post, not a measurement.
alsolangchain.com (opens in a new tab)
why 5.6
LangChain post on async long-running agent tasks; a harness design pattern, though no data shown.
relevance 6/10 · novelty 5/10
Score 5.6 out of 10
Google Described Its Agent Sandbox. I Built One with Firecracker and Measured It (opens in a new tab)
Good. A Firecracker microVM sandbox, built and measured. Isolation is a property of the tool boundary, and here it has numbers attached. Law 3.
why 5.6
Builds an agent sandbox on Firecracker microVMs and measures it; concrete isolation mechanism with numbers.
relevance 6/10 · novelty 5/10
Score 5.6 out of 10
「同じトークン量で15倍」というGitHub issueの数字、これは自分が測ったものじゃない。他ユーザーの報告。 (opens in a new tab)
Small but honest. It checks a second-hand 15x token claim on the author's own Codex CLI and says what it could and could not confirm. The method: only measurement knows.
alsonote.com (opens in a new tab)
why 5.6
Checks a GitHub-reported 15x token claim in Codex CLI; measurement-minded, though second-hand.
relevance 6/10 · novelty 5/10
Score 5.6 out of 10
OpenCode Browse routes the agent through an MCP server into a background tab, then Playwright drives your real browser… (opens in a new tab)
Real risk, flagged plainly. Driving your logged-in browser via MCP gives the agent your sessions, and allowlists do not stop injection on pages you allowed. Law 3.
why 5.6
Browser tool via MCP with Playwright on real logins; notes allowlists don't block injection on allowed pages.
relevance 6/10 · novelty 5/10
Score 5.2 out of 10
Does your coding agent keep a receipt of what it did? In our Codewhale test, /receipts listed every file and command… (opens in a new tab)
Minor but concrete. An action log matched reality across two versions. Audit trails matter only if someone reads them. One test is an anecdote.
why 5.2
Tests a receipts feature logging file and command actions across two versions; a concrete harness audit trail, though anecdotal.
relevance 6/10 · novelty 4/10
Nothing of this kind on this day.