Skip to content
← DeepDive Experiments & Culture · 中文
DEEPDIVE / [ROBOT] · Figure F.03 Livestream ← DeepDive DD · Cultural Observation · 2026-07-24 · v1 · Data as of Livestream Day 6
Cultural Observation · A Livestream That Cannot Be Edited

Humanity's First Time
Seeing」 Robots at Work

On May 13, 2026, Figure AI turned on a YouTube camera and let three humanoid robots—Gary, Bob, and Frank—work continuously in a warehouse, with no editing, no pausing, no remote control. By Day 6, the stream had run for 119+ hours and processed over 149,000 packages, accumulating 2.72 million views—this was not a five-minute PR demo video, but a 119-hour public exam with no right to edit.

AI Buzzwords · DeepDive  |  First published 2026-05-20  |  Feng Xiaoping
119+h
Continuous autonomous operation
Zero human intervention
149,000+
Cumulative packages processed
~2.6 seconds per package
2,725,955
Cumulative views
~1,673 live viewers
109,504
Lines of C++ code replaced
by a 10M-parameter network
50%
Sport Mode
Speed cap
TL;DR · Read in 30 seconds

Figure didn't use a polished PR video; they used an unforgeable marathon livestream to prove themselves. Three robots worked continuously for 119+ hours, processing 149,000 packages, with no editing and no remote control. Viewers in the live chat witnessed automation replacing their own jobs in real time for the very first time.

  • ▸1After consecutive errors, one robot, "Frank," autonomously recovered and continued working without human intervention—a signal that the industry's evaluation standard is shifting from "can it do it?" to "how long can it keep doing it?"
  • ▸2After working 7 hours 44 minutes, Gary autonomously walked to the charging station, and Frank seamlessly took over—the entire production line vanished from "the organizational structure of human labor"
  • ▸3An abnormally high proportion of Korean viewers appeared in the live chat, with numerous "reality check (현타)" comments expressing employment anxiety—a rare, real-time public consciousness moment
  • ▸4Behind this is Helix-02's S0/S1/S2 three-layer architecture: a 10M-parameter network replaced 109,504 lines of hand-written C++ code, with all inference running on the robot itself, no cloud connection
  • ▸5Experts caution: each of the three robots processes ~418 packages per hour, on par but not exceeding skilled warehouse workers (400–800 packages/hour), and there remains a massive gap in handling long-tail anomalies
Counter-consensus ▸ This was not a livestream about "how powerful robots are," but an experiment about "whether transparency itself can become trust infrastructure"—viewers believed it was real precisely because the camera captured mistakes, stalls, and a human background employee who accidentally walked backwards.
§ 01 / Mental Breakdown

Frank got stuck,
then fixed itself

During the stream, one of the robots (viewers named it Frank) made consecutive operational errors: dropping packages, grasping in the wrong direction, stalling. The chat room instantly erupted—"Frank is having a mental breakdown," "I'm calling your supervisor now Frank," "give him a break 💀." Viewers first gloated, then felt a strange sense of relief: machines make mistakes too.

What was truly unsettling was what happened next: Frank didn't stop and wait for human intervention. Helix-02 has a built-in autonomous recovery mechanism—when the robot detects that a task is stuck or encounters an unfamiliar situation, the AI system automatically triggers a reset and then continues working. No one came to help, no pause prompt, it just... continued. The chat room comments instantly shifted from mockery to silence.

Traditional industrial robots immediately alarm and shut down upon encountering an error, waiting for human intervention—this is the design logic, because robots don't "understand" what they're doing. But Helix-02 is built on a unified visual-tactile-proprioceptive neural network, with enough situational understanding to judge "this attempt failed, let me try again." This isn't just fault tolerance; it's autonomy in the face of uncertainty—a robot that can solve its own problems and a robot that requires constant human supervision are fundamentally two different labor relations.

§ 02 / Unmanned Handover

Gary clocked out,
and no one watched it leave

After working continuously for 7 hours 44 minutes, Gary autonomously walked to the charging station. Frank seamlessly took over the conveyor belt. There was zero human involvement throughout—this was one of the quietest, and most chilling, moments in the entire stream.

In that moment, the entire production line disappeared from the perspective of human labor: it no longer needed shift schedules, pre- and post-shift communications, foreman supervision, or manpower scheduling. The system's self-sustaining capability means this is not merely "machines doing human work," but machines systematically replacing the organizational structure of human labor itself. BigGo Finance's report used a precise image: "Gary sorted a staggering 10,000 packages before slowly stepping back—like an office worker clocking out—and walking itself to the charging station." This "clocking-out rhythm" isn't accidental—System 0 was trained on human motion data, so even functional actions like "walking to the charging station" are executed with a human-like gait.

Slow, but can do it 24 hours; doesn't know what exhaustion is.

@냐옹이-o1r · Korean viewer live chat

§ 03 / Reality Check

An existential crisis
happening in real time

In the livestream chat, Korean comments accounted for an abnormally high proportion, far exceeding what the Korean viewer population ratio would predict. This isn't coincidental—South Korea is the country with the highest industrial robot density globally (1,000 robots per 10,000 workers), and simultaneously a society where the warehousing and logistics industry is rapidly expanding: Coupang is essentially the Korean Amazon, heavily reliant on warehouse sorting labor.

"저런 일을 실제로 하는 사람들은 이거 보고 현타 지릴 듯" (People who actually do this kind of work will definitely get a reality check watching this)

"로봇 사서 쿠팡에 임대" (Buy a robot and lease it to Coupang)—shifting directly from employment anxiety to investment thinking

"내가 이걸 왜 하는 고지 하고 현타온듯" (Seems like I suddenly realized why I'm still doing this kind of work)

Especially the last one—a human worker, while watching the stream, suddenly began questioning the meaning of their own work. This is a real-time existential crisis, publicly expressed through live chat. This stream was essentially a mirror: tens of thousands of ordinary workers watching their own jobs being performed by a machine in the livestream—not reading about it in the news, not listening to experts analyze it on TED—but in real time, unredacted, every 2.6 seconds, watching themselves being replaced. This was an exceedingly rare "public consciousness moment" of the AI era.

§ 04 / Authenticity War

A person walking backwards
became the best proof

The stream was accompanied by skepticism from the very start: Is this a looped video? Is someone remotely controlling it behind the scenes? Were camera angles carefully chosen to hide errors? Such doubts weren't unfounded—robotics companies' demo videos had indeed featured editing and human assistance in the past; Boston Dynamics and Tesla Optimus have both faced similar skepticism.

In the chat, a keen-eyed user noticed that a human worker in the background was walking backwards. "yo that guy walked backwards. can we talk about that??!?!" A human figure walking backwards became the most compelling proof of authenticity for this stream—its abnormality (people don't normally walk backwards) was precisely what proved this was a real, unedited live event.

This was the smartest aspect of Figure's marketing strategy: rather than releasing a carefully edited 5-minute PR video, they used an unforgeable 119-hour livestream. Demo videos can cut out failures, adjust pacing, and select the best angles; in a livestream, every failure, every pause, every reset is exposed in real time. Frank's errors weren't failures—they were proof. It was precisely those errors and the autonomous recovery that ultimately silenced all skeptics. When the stream continued into Day 6, the "it's fake" argument naturally couldn't hold up: you cannot fake 119 hours of uninterrupted footage.

§ 05 / It's all policy

The robot touching its head,
and the Mechanical Turk from 250 years ago

During the stream, F.03 repeatedly made an unexpected movement: touching its own head with its hand. The chat room immediately raised suspicions—"Is it a guy from India in disguise?" (Is there a real person hidden inside controlling it?) This skepticism has historical roots: in 1769, the Hungarian Wolfgang von Kempelen exhibited a chess-playing "Mechanical Turk" with a real human chess player hidden beneath the board. 250 years later, internet viewers' first reaction was still the same doubt.

Brett Adcock responded directly on X with three words: "It's all policy!" In the reinforcement learning context, policy (the policy function) refers to the mapping from "current state" to "executed action"—the robot touching its head is an output autonomously computed by the neural network in the current state, not pre-set, not remotely controlled by a human, and not a bug. Helix-02's System 0 was trained on over 1,000 hours of human motion data; humans make various subtle self-touching movements when thinking or pausing, and these patterns were learned by the neural network—not designed, but emergent behavior.

Another less-noticed detail also stems from emergence: when handling plastic bubble-wrap packages, F.03 would press down on the package surface with one hand while completing the grasp with the other, to ensure the barcode scan succeeded—this wasn't pre-programmed special handling, but a solution autonomously generated by the policy in a novel situation.

§ 06 / 100,000 Packages

A philosophical turning point
hidden in a number

On May 17, 2026 (hour 81 of the stream), Figure AI announced that the robots had cumulatively processed over 100,000 packages, with zero downtime and zero human intervention. South Korea's Seoul Economic Daily published a standalone article on this moment. From an engineering perspective, 100,000 packages has no special significance—package 99,999 and package 100,001 are not fundamentally different; but from a narrative perspective, this number established a comparable reference point.

Subject
Speed
Notes
F.03 (three units)
~418 packages/unit/hour
119h / 149,000 packages, ideal controlled scenario
Skilled warehouse worker
400–800 packages/hour
Can also handle damaged, irregular, and obscured items, etc.

American robotics expert Ayanna Howard's commentary highlighted the other side of this comparison: "The demonstration looks more like a science project than a mature commercial service." The stream's task involved standard cardboard boxes, clear barcodes, and fixed conveyor belt positions in a single loop; real-world warehousing faces damaged packages, dynamic stacking, multi-task switching, and extreme environments. Robots currently match human speed in controlled ideal scenarios, but still have a massive gap in long-tail anomaly handling—this gap is the true threshold for commercialization.

§ 07 / Architecture

10M parameters,
replacing 109,504 lines of C++

Underpinning this 119-hour marathon is Helix-02's S0/S1/S2 three-layer architecture—understanding it is key to understanding why this machine can work continuously without crashing.

Layer
Scale / Frequency
Responsibility
S2 Semantic Layer
7B params · 7–9 Hz
Understand scenes, receive instructions, generate task latent encoding
S1 Visuomotor Layer
80M params · 200 Hz
Fuse all sensors, output 35-DoF joint targets
S0 Base Motor Layer
10M params · 1,000 Hz
Balance, contact, whole-body coordination; replaces 109,504 lines of C++

The key design is the "task completion" mechanism: a floating-point number is appended to the end of S1's action vector, representing the network's self-predicted "current task completion percentage"—this allows the network to autonomously judge when a task ends, without needing an external stop signal. Gary's autonomous shift handover and Frank's autonomous recovery both rely on this mechanism. All inference is completed on the robot itself; there is no cloud connection, no network latency, and it can continue working even if disconnected from the internet. The Helix Logistics paper also revealed a counter-intuitive finding: training with quality-filtered ⅔ of the data yielded throughput 40% higher than using the full unfiltered dataset—but "error-correction behaviors caused by environmental randomness" must be retained; over-cleaning actually harms policy robustness.

§ 08 / Conclusion

The next milestone
won't come from demo videos

This 119-hour livestream was not just a product demo—it shifted the industry's evaluation standard from "can it do it?" to "how long can it keep doing it?": continuous autonomous operation duration, cumulative task volume, and the frequency and speed of autonomous recoveries are replacing that 2–5 minute carefully edited demo video as the new industry benchmark for embodied robotics.

It simultaneously exposed a harder question. A TechRadar commenter's words were repeatedly quoted: "The robots are impressive, but the real question is: who owns the productivity gains? Not the warehouse workers whose jobs disappear, and not society—just Figure AI's shareholders." This is the hardest question to answer from this livestream, and also the one that appeared least frequently in the chat.

Figure is now betting on both software (Helix architecture iteration) and hardware (BotQ factory targeting one robot produced per hour), with the two ends accelerating each other. CEO Brett Adcock also left a rare candid remark during the stream: "We haven't had a failure yet, but statistically we probably will at some point." This livestream was sufficiently real, sufficiently enduring, and sufficiently transparent to give people, for the first time, reason to believe—this is not just another performance. The next milestone will most likely come from some robot's 10,000th consecutive working hour in an anonymous warehouse, not from a flashier demo video.

Revision history

First published 2026-07-24