Fetching from the wire…
Public story · 2026-09-26 · high
Self-attribution scored no better than a coin flip across 15 model-benchmark pairs, and what looked like self-preference tracked code length instead.
Why now: The paper posted to arXiv covers all fifteen model-benchmark combinations as of September 26.
Researchers tested whether large language models can recognize code they wrote versus code another model wrote, across MBPP, HumanEval and DS-1000. They couldn't. Single-solution self-attribution reached 49 to 58 percent balanced accuracy in all 15 model-benchmark combinations tested, per a paper posted to arXiv. That's chance.
The more interesting failure showed up in a different test. When models picked between two solutions and were told one was their own, the "pick your own" accuracy correlated at r=0.93 with how often the evaluator's own solution happened to be longer. Models weren't recognizing their own style. They were rewarding length.
The researchers checked this by stripping docstrings, comments, type hints and local variable names from the code before re-running the test. Pass@1 held steady, so the code still worked the same. Ten of twelve re-tested results dropped to chance, and Claude Haiku's self-preference disappeared entirely. A trained classifier could still separate most of the normalized pairs, so some signal survives stripping. It isn't self-knowledge. It's leftover style.
This matters for anyone building systems where one model judges another's output, a pattern showing up in eval harnesses and multi-agent pipelines that use an LLM as a critic. If a judge model shows a preference for one model's code over another's, the paper's findings suggest checking whether that preference tracks solution length or formatting before treating it as evidence of quality, provenance, or collusion between models. The paper doesn't say whether normalization changes outcomes in production judging setups, only in this benchmark's pairwise comparisons.
Each link below shares sources, entities, or timing with this story.
Ockhamareto (arXiv 2608.24473) reinforces a unit-test rollout only when it's non-dominated on both mutation-killing and test count, then ties each test's killing power back to specific source tokens. Against MIST-RL that's a 3.4x better per-test trade-off, plus 30 to 35 percen...
This is the most complete production-agent build sheet I've seen anyone publish, and almost every number in it argues against how the rest of us are building agents. Replit disclosed the internals of two production agents at SaaStr AI 2026: 10K, an autonomous VP of Marketing,...
A July 28 study on HumanEval+, MBPP+, and LiveCodeBench found real original tests moved Qwen3.6 on LiveCodeBench from 13.1% to 39.4%, while stronger-model-generated synthetic tests added 1.7 points at p = .701, statistically indistinguishable from nothing. Spend your retrieval...
Across 1,800 AdvBench cases, injecting malicious reasoning alone was inert at about 0% success. Pairing it with a short output prefix pushed attack success as high as 99% on Gemini 3 Flash, DeepSeek V4 Flash and Claude Haiku 4.5, and contextual prefixes beat static ones. (arXi...
Enterprises provision agents like employee-owned hosts: a static credential set fixed at deployment covering everything the role might ever need, every credential exposed whether or not the current task uses it (arXiv 2609.15422). This paper implements the gate for a three-sou...
If you have a CLAUDE.md, you're in scope. Today. arXiv 2607.14611 (cs.CR, filed July 16) evaluates prompt injection planted in the persistent memory files that agentic coding systems write and re-read across sessions. The researchers tested both Anthropic's Claude Code and Ope...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.