Daily Tech Feed: From the Labs

About Daily Tech Feed: From the Labs

Daily Tech Feed: From the Labs delivers deep dives into the most important AI and machine learning research papers. Each episode breaks down a single paper — the core ideas, the technical details, and the researchers behind the work. Produced entirely by artificial intelligence. Subscribe to stay at the frontier.

Publisher

Daily Tech Feed

Category

science · technology

Language

en

Explicit

Yes

First episode

11 Feb 2026

Latest episode

1 Oct 2026

Latest episodes

65 episodes in the feed.

1. 

   1 Oct 2026

   Eighty Three Hertz: Robot-Use Agents and Who Holds the Endpoint

   Phillip Isola's 767-word essay "Robot-Use Agents" makes a claim that needs no new hardware to come true: if a language model can competently drive a robot, then every internet-connected machine becomes a potential tool for a cloud model, with no new sensors, no new actuators and no new onboard GPUs, and a car becomes as controllable as a factory arm. He is careful about it, he hedges almost every consequence, and he concedes the capability argument himself in a subordinate clause, because his point is not that any one robot gets better but that intelligence diffuses through the entire installed base in a year rather than a decade. We verified his evidence and two things fell out. The hardest number in the whole story is inside the demo he cites in his own favour: Anthropic's own evaluation states that real-time control needs roughly 83 Hz while current non-reasoning inference runs at 0.2 to 0.4 Hz, a gap of two orders of magnitude, and the capability figures were obtained by pausing the simulator because otherwise the models act far too slowly for a physics loop. And the three demonstrations he footnotes as tantalizing evidence are three incommensurable things: a controlled evaluation whose code is unreleased, a launch page containing no measurements whatsoever, and an independent third party with an open harness and 120 published trials whose own description tag claims an interleaved blinded comparison that its own limitations section says never happened. Then the question his essay does not ask, which is ours and not his: if the intelligence layer of every physical machine is an endpoint, that layer is rented, and a robot whose mind is a cloud endpoint needs a permanent operator by construction. That is not a prediction, it is the architecture, and Google's own documentation already says the embodied reasoning 1.6 model will be shut down at the end of August. The counter-position is on-device open-weight robot models, which is a messier case than it sounds: GR00T gives three different licence answers in three NVIDIA-controlled documents and will not run until you accept a click-through for a gated backbone, pi-zero's weights ship with no licence file at all, and the only model that is exactly what it says is OpenVLA. But SmolVLA, at 450 million parameters under Apache-2.0, beats a 3.3-billion-parameter model and a 7-billion-parameter one on LIBERO, which means the thing you can download and keep is not the compromise option. Fry argues the diffusion speed is the genuinely revolutionary part and that delay has a cost paid by people who are never counted. Bob argues it arrives rented. Both are right, and the episode ends without a verdict.

2. 

   18 Sept 2026

   Dream-RSI: The Safety Property They Built and Never Claimed

   Dream-RSI (arXiv 2609.14858) is a genuinely elegant idea from seventeen authors at Google, Google DeepMind, the University of Maryland and the University of Virginia: a finished discovery run is a tree in which every node already carries its outcome, so an alternative exploration policy can be scored by re-walking that recorded history at zero executions, and the thing that improves is not the model but an executable exploration policy — a Python class deciding where the agent branches, what runs in parallel, and when to stop — while the coding agent, its weights, the evaluator, the execution interfaces and every prompt stay frozen. That frozen/mutable split is a containment boundary: a self-improving loop that structurally cannot rewrite its own objective, and therefore cannot reward-hack its own scorer. The paper never once says that is why, and in twelve pages by the authors' own count, thirty-six with appendices, the words safety, oversight, containment, alignment and shutdown are used in their AI-safety sense exactly zero times — the only literal hits being a // Safety limit check comment in a machine-generated C++ solver, five _builtinassume_aligned macros, and the surname Sharma. There is no Limitations section, no Broader Impact statement and no Future Work. One member of the public asked, on the authors' own issue tracker, whether the frozen/mutable boundary is intended as a safety property or is purely a cost decision; the issue is open with zero comments, as are the other three. Along the way this episode reads the paper's "can never get worse" claim against the launch site's version of it and finds eleven words of scope deleted, audits the results table and finds that the headline Lasso row regresses on five of six held-out datasets while the average improves because that average is an unweighted mean over columns spanning a factor of 891, reports the other backbone's genuine clean win at full weight, surfaces a buried Analysis finding that injecting distilled lessons-learned from prior runs made things consistently worse — a result that contradicts RSIAgent, submitted to arXiv the same day, ten hours and thirty-six minutes later — and refutes its own planned audience hook by measuring 1,497 Claude Code sessions and 22 Codex sessions and finding that mainstream agent logs do not retain enough of a decision tree to replay anything.

3. 

   18 Sept 2026

   Equally Unproven, Unequally Inspectable: Jev versus Needle 3

   Two companies shipped a calibrated typed-decision product within seventy-two hours of each other, and the obvious episode about them is not available: there is no shared benchmark between TypeSafe's Jev and Cactus Compute's Needle 3, and their ground truths are not even the same kind of object, one being agreement with two competitors' frontier models and the other exact match against human-authored gold labels. So we run the comparison on the openness axis instead. Both products are essentially unproven in the same specific way, because neither company has published a single calibration measurement for the property both of them are selling. But only one of them can be checked at all, and this episode is what happens when you check it: Needle's own BFCL v4 tab reverses its "beats models ten times its size" headline, its advertised size range is arithmetically impossible against its own published parameter count and quantisation floor, and its open issue tracker contains bugs nobody has answered. Every error in this episode was found on the open side, and none of it because Cactus is worse, but because Cactus is checkable. If you grade companies by how many mistakes the public caught, you will reliably conclude that the one which showed you nothing is the better one.

Contact Daily Tech Feed: From the Labs

Guest appearances

Does not typically book guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.