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.

Daily Tech Feed: From the Labs is a technology podcast hosted by Daily Tech Feed, with 64 episodes on record and a Required Pod Score of 80.

Daily Tech Feed hosts Daily Tech Feed: From the Labs, a technology show with 64 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #67

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

  Oct 1, 202634 min

  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.

  ListenShow Notes
• 

  Episode #65

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

  Sep 18, 202652 min

  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.

  ListenShow Notes
• 

  Episode #66

  Equally Unproven, Unequally Inspectable: Jev versus Needle 3

  Sep 18, 202640 min

  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.

  ListenShow Notes
• 

  Episode #64

  RSIAgent: The Thing That Improves Is Not the Thing That Does the Improving

  Sep 16, 20261h 6m

  Four days after we read a seventy-five-page roadmap asking what genuine recursive self-improvement would architecturally require, six authors from Aether AI, UC San Diego and the University of Illinois Chicago shipped a paper claiming a working instance of it that never updates a single weight. RSIAgent (arXiv 2609.15364) is a training-free multi-agent harness: an actor that acts only by writing complete Python or Bash programs and is the sole role allowed to write memory, an independent verifier that can return PASS, FAIL or UNVERIFIED and inspects behind a restored QEMU checkpoint so its probes never enter the scored state, and a curriculum agent that decides what to practise next and never grades anything. The system explores a piece of software broadly and then deeply, writes down what it learned, freezes those notes, and goes to work. The "reusable causal structure" the abstract promises turns out to be a directory of actor-authored markdown files with, in the paper's own words, "no required schema, file count, or length" — roughly 150 to 320 kilobytes of notes per task, and no causal graph, do-operator or structure-learning algorithm anywhere in the paper. The headline is real and so are the qualifications the abstract leaves out, all of which the authors print themselves in Appendix C: the cross-system comparison "does not use a matched evaluation protocol", RSIAgent loses to GPT-6 Astra on ALE binary accuracy at 50.75 against 52.24, only 41 of 82 OSWorld tasks and 19 of 67 Agents' Last Exam tasks actually received any self-improvement with the rest retaining baseline scores, the explored tasks were selected because their baseline was below full credit, and Appendix A's first sentence calls the whole thing "the target-conditioned reference implementation" — the curriculum agent holds the scored query throughout and the deep stage attempts the scored task itself up to five times before the memory is frozen. The harness without any self-improvement already beats GPT-6 Astra on Agents' Last Exam, 83.75 against 82.26; self-improvement then adds 1.07, which is smaller than that benchmark's own published run-to-run standard deviation of about two points. On OSWorld the self-improvement contribution is decisive and internally controlled, plus 7.01 under an identical harness. We traced the largest single gain in the paper and it is rubric-shaped learning: on the video-editing task both runs remove the watermark and preserve the proportions, and the memory run scores 0.60 higher because it learned to express the crop through the native Shotcut filter the scorer searches for. Measured against episode 0062's ladder, RSIAgent clears persistence, clears strategy, clears the learning agenda with an asterisk, and stops dead at deployment and inheritance — by design, because the curriculum agent and all memory writes are switched off before the system is measured, and because the curriculum prompt, the verifier prompt, the stopping policy and the budgets are fixed by humans and never touched. The thing that improves is not the thing that does the improving. That is a smaller claim than the title makes, it is better supported than the title, and it is more useful to anyone who wants to build something this week.

  ListenShow Notes
• 

  Episode #63

  Jev and the System One Model: A New Calling Convention

  Sep 16, 202648 min

  TypeSafe AI came out of two years of stealth on 15 September 2026 with a model called Jev and a category name they coined for it, the System One Model, and the interesting thing they shipped is not a new kind of intelligence but a new way of calling one. Instead of chat(messages) returning a string, you get a function of state and questions returning typed values with calibrated probabilities on them: one blob of state, many isolated typed questions, one parallel pass, no strings ever. Three primitives carry it. Choice picks one of up to 255 supplied options and returns the whole probability vector plus a confidence scalar; Score returns a continuous value against labelled anchors; Noul returns a Bernoulli, with no separate confidence field because for a Bernoulli the probability is the confidence. Questions are evaluated in parallel and in isolation against the same state, so latency is roughly flat in the number of questions and question twelve cannot be contaminated by question three, and the price of that isolation is that composition moves into your code. The efficiency result is real and needs none of the marketing around it: on TypeSafe's own published workflow eval Jev scores 67.8 percent overall, exactly tied with sonnet 5 and 6.3 points behind the leader sol at 74.1, at four ten-thousandths of a dollar and four tenths of a second per case against sonnet 5's twelve cents and 78 seconds, which is 293 times cheaper and about 195 times faster at identical accuracy. The same eval contains the clean demonstration of where the thesis breaks, published voluntarily and un-headlined: Invoice Processing at 61.8 percent against 79.1, a 17.3-point gap where every other gap is two to five points, on the one workflow that is multi-hop arithmetic across three documents. Two academic literatures arrived at this interface first, and the episode walks both: grammar-constrained decoding from May 2023 through Outlines, llama.cpp grammars, OpenAI Structured Outputs and XGrammar, which had made guaranteed-valid structured output free on a laptop for three years and four months before Jev launched; and the schema-driven encoder line from GLiNER to the GLiNER bi-encoder, which published the fix for Jev's most-complained-about limit, the 255-choice ceiling, seven months earlier. An Apache-2.0 model shipped an overlapping guarantee at 74 million parameters the same afternoon and got a twenty-sixth of the attention, and somebody approximated the interface on a laptop within hours. What nobody open has shipped is the calibration training, which is the only genuinely hard-to-copy part of this, and the company named after calibration published no calibration measurement of any kind, no expected calibration error, no reliability diagram, no Brier score, no log loss. The last two chapters take the robotics reading seriously enough to read a datasheet: a twenty-dollar optical flow sensor returns delta-x, delta-y, a surface quality metric and a shutter value, is blind below 80 millimetres, drifts without bound and cannot be converted to millimetres without a rangefinder, and in every shipped vision-language-action system the slow semantic layer is buffered behind something fast and local. Jev does not supply that layer and does not claim to; TypeSafe make no robotics claim at all, and the robotics reading is ours.

  ListenShow Notes

Recent guests on Daily Tech Feed: From the Labs. Study who booked and why before you pitch.

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.