The robot didn’t go rogue. We just forgot to build a big red button

Last week, a viral video filmed at a U.S. restaurant showed multiple employees physically wrestling an entertainment robot, alarming diners
Blogs
"Turn it off” needs to be obvious, immediate, and practiced. Pic: Pixabay

24 March 2026

We tend to picture robot danger as something dramatic: a military drone, a rogue algorithm, a sci-fi headline. Then a restaurant bot in California reminds you that the near future is much smaller, much messier, and occasionally involves smashing your crockery.

Last week a viral video filmed at Haidilao, a hot pot restaurant in Cupertino, saw an entertainment robot that danced too close to a table, started flinging its arms, and sent plates and chopsticks flying, forcing staff to physically restrain it. Haidilao later said it was in “celebration mode” and had been brought closer to diners at a customer’s request and in a tight space.

In other words: not an uprising. Just a demo pushed out of its safe operating envelope by a customer who wanted the robot nearer the action, and by a system that apparently didn’t have a hard, reliable way to say “no, too close”.

 

advertisement



 

This is where the kill-switch question stops being a nerdy footnote and becomes the whole story.

The footage shows multiple employees physically wrestling the robot back while one appears to be working a phone, as if trying to stop it via an app. Maybe there is an emergency stop. Maybe there isn’t. Either way, the point is the same: in the moments that matter, “turn it off” needs to be obvious, immediate, and practiced, not a hidden UI path, not a permissioned feature on one staff member’s handset, not something you discover mid-chaos while a machine continues to fling its arms around.

Robotics people sometimes talk about human factors like it’s a soft concern. It’s not. Human factors are the difference between a harmless spectacle and someone getting scalded by a hot pot because the robot’s dance routine has no sense of proximity, risk, or consequences.

Here in Ireland we’re already doing restaurant robots, just mostly the boring kind – and for good reason.

Dublin restaurant Senbazuru Izakaya’s robot waitress Bella (the BellaBot model from Pudu Electronics) is a wheeled service robot with an adorable cat face that brings dishes to the table, sings a little tune, and otherwise stays in its lane. No swinging arms. No surprise torque. Less dancer and more delivery trolley with vibes.

Dublin Airport has a similar BellaBot. Most of us have probably either seen social media posts showing the friendly cat bot bringing plates to diners at The Fallow Kitchen & Bar, or had it deliver food to our own table while waiting on a flight.

The contrast matters. These cat bots and tray robots in general are designed for narrow tasks: they move along predictable routes, carry things, avoid collisions, and then stop. Humanoid entertainment robots are designed to perform, which means unpredictable movement and, of course, customers treating them like props. Haidilao itself said the incident happened because the robot was moved into a closer-than-usual setting. That is exactly what will happen in any customer-facing environment because people are people. They will crowd it, tease it, film it, and push it into edge cases for laughs.

So, f you’re a business looking at robots as a wow factor, the cynical lesson is that your real innovation isn’t the robot. It’s the controls around it. The big red button that staff can hit without thinking. And defining clear rules for how close it can get to diners. Also, maybe most importantly, staff training that assumes customers will do the stupid thing, because customers always do. And a product that defaults to safe refusal when it’s nudged out of its operating space.

Because the future isn’t just about whether robots can dance. It’s about whether we’ve built a world where someone can flip a killswitch when needed.

Read More:


Back to Top ↑