🐬 OpenWhistle is Spotlight @ NeurIPS2026 (top 1.3%)!
We release the largest open dataset of dolphin whistles (114h), enabling ML at scale to better understand one of the most complex non-human communication systems.
Led by @FMustun & @chiara_semenzin
📄 https://t.co/jeTvlmQQnk
did a group presentation today with @3blue1brown's manim style transitions. Sharing the template for anyone to build upon
Brought to life with @NarekMaloyan's manim-web + reveal.js + claude + codex
view template: https://t.co/LOSKmrtlXa
view repo: https://t.co/gTb9xxYp7F
I have talked much about the "bitter lesson" of computer vision, arguing that many of the intermediate tasks that vision has solved traditionally - 3D reconstruction, segmentation, tracking, etc - are not necessary to build AI that understands the world through vision... (1/n)
🎉 Native, encoder-free VLMs are an important step toward more unified multimodal intelligence.
We’re also pioneering this paradigm with our NEO & SenseNova-U series:
- NEO: https://t.co/qooHtOdaM6
- SN-U: https://t.co/U2uOLI1ISL
Excited to see the field move forward together!
Google just open-sourced Harness².
(turn any harness into a self-improving system)
a harness is everything wrapped around the model, like the system prompt, tools, memory, skills, and subagents. today a person designs it once, and the agent runs every new task with that same fixed setup.
Harness² lets the agent refine that setup for each new task on its own, with the model weights left untouched.
on every task, the agent proposes edits to its harness, runs a few candidate versions, and composes a better harness by comparing how those runs behaved.
because it learns from the differences between runs, it needs no correct answer or grader for the task.
that covers a single task. Harness² also carries what it learns from one task into the next.
after each task, it saves the harness it settled on along with the lessons that held up across the runs. the next time it refines a harness, it starts from those notes instead of from scratch.
this means every finished task makes the next round of edits more informed.
Google tested this with Gemini 3.5 Flash and GLM-5 on legal, office, and professional work benchmarks. one round of edits was enough to beat their original harnesses, and giving the agent more rounds pushed scores higher.
those extra rounds can go wide or deep. the agent either tries several candidate harnesses at once or keeps refining a single one step by step, using OpenCode or Codex to carry out the work.
you can find the Harness² repo here: https://t.co/i00WLeeFpw
I wrote about a similar idea for agents already running in production, where the harness should repair itself after a failure instead of waiting for someone to debug the trace by hand.
that piece walks through how @Cometml's Opik (open-source) closes this loop, going from a failing trace to a proposed fix to a regression test that stops the same failure from coming back. it's quoted below.
绝对是本周最值得读的文章之一,来着 Claude 团队的 Felix 的个人博客。
一篇帮助你理解如何更好地与 AI 协作,如何更聪明地使用 AI。
在这个能力每隔几周就突飞猛进的世界里,我们需要一些技巧,让我们能够做到以前从未想过或认为不可能的事情。
其中有个对我有启发的点:
关于如何把一件事情做到极致的指令或思路:坚持使用业内顶尖专家使用的工具;选择一些看似不切实际的目标,然后告诉模型这些目标非常合理;挑战你的认知,创造新知识,使用外部评判者。
甚至还搭配了一个提示词:
我想要的是一个更深入的版本,而不是一个更大的版本。在重写题目之前:(1)请说明该领域的顶尖专家会做哪些我没有要求的事情;(2)请列出他们会从哪些最原始的素材入手,而不是我已经整理好的素材;(3)请列出他们会使用的具体方法和工具;(4)除了你我之外,还有什么可以证明结果是正确的。然后,请修改我的题目,使其完全符合上述要求。
A great read. The blog post captures years of progress in mechanistic interpretability and offers an optimistic vision: perhaps we really can open the black box and understand how neural networks work.
I share that optimism, but with some reservations.
I'm skeptical of explanations that stop at individual neurons, accompanied by compelling visualizations that seem to "explain everything."
Humans are remarkably good at convincing themselves. It's easy to cherry-pick evidence that supports a hypothesis, especially when the visualizations look convincing.
I'm also not convinced that "Recursive Generalization" is fundamentally different from hierarchical representation learning. As representations become more abstract, they discard details while preserving invariances. Isn't that essentially what hierarchical representations have always been about?
IMHO, we need to move beyond a largely descriptive, behavioral approach toward a principled mathematical framework. And we have a natural starting point: gradient descent.
Rather than just asking what a network has learned, we should understand why learning dynamics produce these structures in the first place.
Of course, this is extraordinarily difficult. Look at OpenAI's 719 mathematical proofs. We see plausible proofs tackling problems at the Fields Medal level, yet no comparable breakthrough that cracks deep learning theory. That contrast is striking.
Part of the difficulty is that there are countless plausible theories of how deep networks work. Proving even one can be mathematically formidable. And a proof alone isn't enough. Each theory needs empirical validation, often requiring substantial GPU compute. It's a daunting combination of mathematical and experimental challenges.
Still, I believe this is the way forward. Interpretability gives us observations and hypotheses. But ultimately, we need a theory that explains why these phenomena emerge from the learning process itself.
That's how we turn compelling stories about neural networks into actual understanding. And hopefully recursive self-improvement can help with that 😀
This is f*cking gold..
A Chinese lab just dropped "The End of Documentation" and it reads like an obituary for every README on GitHub.
The claim in one line: documentation is a rumor about the program, the artifact is the truth.
The text was written once, at release. The code moved on the next morning. Every agent built on the docs is built on a memory.
The fix is one reading procedure the model runs on the artifact itself. Six steps: inventory, structure, behavior, data flow, rebuild, verify until the diff is empty.
Across 26 systems the recovered spec beat the official docs in 23 and surfaced 61 behaviors the docs never mentioned.
So you stop being the person who reads the manual. You become the person who points: you choose what gets opened and you check the diff.
Docs turn disposable. The artifact turns into the job.
That is the exact system I run with REA + Kimi K3 and documented below: one prompt, 14 binaries, 14 rebuildable specs, zero docs opened.
The whole paper in one line: the program is the spec, the model is the reader ↓
Representation conditioning is better than representation alignment.
The two recent papers reported similar observations. Time for some new trials?
RECON: https://t.co/Zc5HEnU4BN
Dino forcing: https://t.co/yBW8IgNy4f
S4VY is an incredible advancement in the field of real-time 4D joint segmentation and depth prediction! We’ll be releasing the code and checkpoints soon, so stay tuned for more updates.
Very ambitious work by Seungone on trying to figure out if LLMs can actually write strong follow-up papers across the natural sciences.
Based on our previous work on automated paper review, we apply rigorous standards to the generated papers and find that even with frontier models, none are hallucination-free and meet the bar of the scientists working in each domain.
We believe that this poses a challenge for upcoming LMs, can they actually do an end-to-end research work and generate an artifact that could move science forward?