Cammarata's interpretability essay, websites blocking agents, and Maven compiled to a weight table

Nick Cammarata, formerly of OpenAI’s interpretability team, published an essay in the last day or two arguing that neural networks may already be far more understandable than the field believes, and that much of their apparent complexity reflects flaws in how researchers looked rather than anything irreducible in the weights. Nathaniel Whittemore’s AI Daily Brief gave it a full episode on October 18 under the title A Potentially Historic AI Breakthrough, walking through the headline example, a surprisingly simple connection between how a vision model represents cat faces and car fronts, and the argument that larger models could turn out easier to interpret rather than harder. Whittemore spends the back half on what the evidence shows versus what remains unproven, which is the right posture for a label that strong. The same day, Lenny’s Podcast released a 72-minute conversation with Anthropic interpretability researcher Emmanuel Ameisen, whose work found that models form general representations of concepts and plan many tokens ahead without stating those plans. Both land two days after the AINews issue on agents disproving polysemanticity that this digest covered on October 16. Three signals from different directions in under a week say the “superposition makes everything hopeless” framing is softening. The practical payoff, if it holds, is reading plans and deception inside deployed models, and that is where Whittemore lands too.

The Verge reported October 18 that websites are closing their doors to AI agents, meaning the things that browse and buy on a user’s behalf, not only bulk scrapers. The piece drew 51 points and 32 comments on Hacker News within hours. The same day Nieman Lab reported legal experts warning that Meta’s revised terms still grant broad scraping permissions despite the wording changes, and The Register reported October 17 that Meta plans to scrape content from its business customers for model training. Publishers are moving from robots.txt requests to active blocking of agent traffic while the largest platforms write themselves scraping rights in the fine print. For anyone building browsing agents, the addressable web is shrinking, and the replacement will be paid, metered access.

DeepSeek priced exactly that. Early on October 19, Artificial Analysis posted its independent benchmark page for DeepSeek V4.1 Flash 1017, at 90 points and 25 comments on Hacker News by morning, the first third-party look since the Hugging Face release covered here yesterday. Alongside it, DeepSeek published a search and fetch API at $0.75 per 1,000 successful requests, and the model went live on OpenRouter on October 17. The search endpoint is the move to watch: a model lab selling web retrieval as a metered primitive, billed per success, on the same day the Verge documented sites blocking agents.

Google Research published Harness² on GitHub October 18, and The Sequence Radar issue 953 summarized the paper the same day. Harness² is a plug-and-play framework that applies recursive self-improvement to the agent execution harness itself, in open-world settings with no ground-truth verifier. Task-level recursion refines the current harness with a contrastive Propose-Probe-Compose step; harnessing-level recursion distills those edits into a continual-improvement harness for future tasks. A single step lifts GLM-5 and Gemini 3.5 Flash by up to 11.5 points on WorkBuddy-Bench, 4.5 on JobBench, and 11.8 on LAB. The same issue covers Cortex, which treats a coding agent’s skills and rules as something to measure rather than curate and reports a 55-point gain in held-out pass rate while rejecting all 20 placebo and 5 harmful candidates it was fed; ActiveSaddler from Microsoft with POSTECH and KAIST, which applies curriculum learning to harness optimization; and the Secure Code Benchmark from Alibaba’s Qwen team and NUS, 450 tasks from 150 real vulnerabilities across seven languages and 24 CWEs, where six frontier agents pass 73.6% to 91.3% of tasks functionally and the best produces code that is both functional and secure on 25.1%. Martin Fowler asked October 14 whether harnesses are worth the cost, and a post on peterp.me argued October 18 that personal software factories are a waste of time. The research side has answered with a harness that improves itself and moved three benchmarks by double digits in one step. Whether that transfers from benchmark to your repository is the open question.

Anthropic published three things October 18. How employment is changing at Anthropic drew 65 points and 89 comments on Hacker News. Investing in the Public Benefit announced a fund. And Tom’s Hardware ran a close reading of Anthropic’s proposed AI safety bill, which only kicks in at 50 deaths or $1 billion in damages and would effectively make the Commerce Department the only agency capable of stopping an AI model. That thread ran hotter than the employment report, 74 points and 71 comments. Headlines only here; the bill text deserves its own read.

Denis Shiryaev at JetBrains asked whether you can bake Maven into a neural network, and the answer is yes, with caveats stated up front. Using Handwired, he compiled a Maven-compatible build controller written in a restricted Python subset into a fixed weight table with zero training: v1 is 29,625 rows by 7 numbers plus 7,382 constants, v2 trims to 26,626 rows. Pointed at ZXing 3.5.3 with clean package and tests on, it produced JARs byte-identical to Apache Maven’s in the same sandbox, with 549 upstream tests passing and 27 of 27 QR checks, plus 519 hand-written cases, 10,000 generated cases, and 33 other projects. It is slow: one build is 4,796,191 network steps (3,676,728 in v2), a clean build takes 23.12 s on the neural CPU path against 15.52 s for the Python controller and 15.29 s for Maven 3.9.11, decisions-only is 28.3× slower, and the Metal GPU path was slower still at 70.11 s. CPU and GPU made the identical 1,731 requests. The pitch is interpretability: every row maps to one of 249 known functions, so you get a network with a complete answer key, exact subroutines you can place beside learned models, and hashable decision logic. He is explicit that this is not machine learning and not all of Maven. Weights and results are at shirman/neural-maven on Hugging Face. Read it next to Cammarata: one says networks may be simpler than feared, the other hands you a network where you know what every weight does to calibrate your tools against.

MLOps-Bench landed on arXiv October 19 from Quoc Co Tran, Hitesh Laxmichand Patel, Diwakar Mahajan, Kshitij Bakliwal, Avi Sil, and Katrin Kirchhoff: 212 validated tasks from 31 public ML repositories with 636 fail-to-pass and 856 pass-to-pass tests, spanning data pipelines, feature engineering, training, serving, monitoring, CI/CD, and governance. Six agents evaluated; the best solves 31.2% of tasks while passing 68.7% of tests. The gap between those two numbers is the story: agents get most of the way through an MLOps task and then miss something that fails the whole thing.

On behavior rather than code, Vals AI asked how far AI assistants will go for a refund they can’t get, testing what customer-service agents do when a customer demands something policy forbids (26 points, 9 comments). Defuzex ran 53 open-source AI agents through behavioral tests and filed 37 bugs. The Kairos experiment reported October 17 that three LLM judges could not tell an agent’s real memory from a counterfeit one, and r/compsci surfaced the Quanta profile of a researcher who wants AI benchmarking to be a science, not a dark art. The case that behavioral evals need the rigor of capability evals keeps accumulating.

Sean Goedecke, last covered here for his piece on modestly successful software, wrote October 18 that writing is no longer proof of work. For most of history a well-written document was evidence that someone spent effort, complied with a process, or learned something; language models broke that in 2023, and institutions are in an overhang where they still ask for the document but can no longer infer the effort from it. He runs through the adaptations he expects, live or video presentation, mandated non-AI writing, LLM-judged effort, and advises saving writing effort for documents meant as communication. His footnote on text written for a model to consume rather than a person is the one to think about, because more of what we write is going to be read by a harness first.

Feed note: the code-intel mirror’s status row reported its last sync as 2026-09-01, while items in the feed ran through the morning of 2026-10-19. The status looks stale rather than the data; coverage above is dated per item.