The flashy company, which recently completed a blockbuster IPO, appears to be leading the pack of humanoid robot makers.
Increasingly, companies are building humanoid robots that perform impressive athletic feats to mark the field’s progress. Now, Chinese robotics company Unitree says its new “Superman” robot can run 12.66 meters per second, faster than Usain Bolt’s top recorded speed.
Getting a humanoid robot to run at all requires split-second control and has been a significant engineering challenge occupying roboticists for decades. That’s why sprinting, as well as jumping, have become popular targets for robotics companies keen to demonstrate their technology’s prowess.
Unitree’s latest demonstration pushes the boundaries by not only outrunning the fastest human ever, but also jumping around 6 feet 7 inches into the air from a standing start, a full foot more than the human record.
“This new machine has only been in development for a little over three months, with significant room for further improvement in the coming months,” Unitree said in an X post that accompanied a video of the accomplishments.
The records have not been externally verified, and the sprinting speed was a peak reading taken over a shorter stretch rather than a full 100 meters like Bolt’s record. The robot’s legs are also only 2 feet 9 inches long, according to Unitree, which results in an ungainly, arm-waving gait while running.
The effort is nonetheless impressive and adds to Unitree’s growing reputation as the company leading the pack of humanoid robot developers. And the timing of the announcement was no accident, coming just days before Unitree’s stock market debut and shortly before the World Humanoid Robot Games, which opened on August 22.
The company’s Shanghai IPO was a blockbuster, recording an initial 629 percent gain on the company’s first day of trading. It was briefly valued at around $66 billion before closing at a more modest $51 billion. However, some analysts have cautioned the excitement around the company’s technology may be getting ahead of market realities.
“The IPO is expensive, and the investment risk is already quite high,” Wang Zhuo, partner of Shanghai Zhuozhu Investment Management, told Reuters. “Unitree generates much of its sales from research and demonstrations, but wider application is still far away.”
But the company holds a dominant grip on the emerging humanoid market that may justify some of the hype. Chinese firms control roughly 90 percent of the global humanoid robot market, with Unitree alone shipping 5,500 of the 13,000 to 18,000 humanoids sold worldwide in 2025, the most of any manufacturer. In contrast, US humanoid champions Figure AI, Agility Robotics, and Tesla each shipped around 150 units.
China’s success is down to “a combination of policy support, public investment, mature supply chain, and advancements made in AI software and hardware,” Lian Jye Su, a tech analyst at consultancy firm Omdia, told Rest of World.
This is leading to an increasingly combative response from the US. On July 29 the Federal Communications Commission banned new imports of foreign-made humanoid and quadruped robots. The move was framed as a matter of national security, though it has also been seen as an attempt to give domestic developers a leg up.
Beijing predictably objected, with foreign ministry spokesperson Mao Ning telling a press conference that “protectionism does not make the US more competitive, and it will only hurt the interests of US companies and consumers.”
Given the rapid progress made by companies like Unitree, it seems likely it’s going to take more than trade barriers for the US to catch up. In the meantime, we might see more human athletic records fall to China’s leading humanoid developers.
Implicit neural representations can turn massive scientific measurements into compact functions. A hierarchical approach now helps these representations preserve richer fine-scale detail.
While the tech giant has always focused intently on protecting proprietary data, its database security capabilities are taking on new importance as agents increase vulnerabilities.
Moving live voice agents from demo to production requires rigorous, automated testing to handle the unpredictability of real multi-turn conversations. ADK now provides native live evaluation, allowing developers to test graph-based agent workflows against LLM-driven simulated users that generate actual audio via Gemini TTS. By defining evaluation scenarios and natural-language rubrics, you can automatically score audio responses and tool executions, inspect the resulting transcripts in ADK Web, or run the CLI directly in your CI/CD pipeline.
Between July 2024 and February 2025, Adobe recorded a 1,200% increase in traffic to U.S. retail websites from generative AI sources. That figure alone would be notable in any industry. For anyone tracking the broader shift toward automation and machine-led decision-making, it’s a signal of something larger than a marketing trend, it’s the early shape […]
Put several AI bots to work, and a mistake by one may not stay within its assigned task. For example, that error could reach another bot’s files and login credentials, or even the computer running them all. Two releases this month offered companies very different ways of containing that risk.
On August 17, Nous Research announced that its Bot Mode would ship bundled and enabled by default in Hermes Agent v0.20.3, turning agent profiles into a roster of named bots that hand off work to one another. About a week earlier, SpaceXAI launched Grok Bot with almost the same interface: a sidebar of named teammates who sign in to your tools and keep working long after you close your laptop.
The interface converged within a week, but the answer to the question every platform team has to ask did not: When one bot goes wrong, what can it reach?
Four projects have now come to their own answer, and no two of them agree.
Grok Bot draws the line around the user account.
Hermes draws it around the profile.
OpenClaw draws it around an optional runtime sandbox.
Taken together, the documentation shows an industry converging on the persistent coworker interface far faster than it is converging on what constitutes an identity or a security boundary for it.
Four projects, four written answers
Every one of these products now offers the same surface. You create several named agents, assign them different jobs, and have them pass work among themselves. The naming convention alone suggests separation, since a bot called Expense Manager and a bot called Talent Scout sound like they occupy different rooms in a shared office.
The documentation says otherwise, and it says something different in each case. The unit of isolation is the account in one product, the profile directory in another, an opt-in container in a third, and the deployment topology in the fourth. Those four units are not interchangeable, and an operator who assumes the roster itself is the boundary will be right in exactly one of the four cases.
Is Grok Bot confused about what it wants to be?
SpaceXAI’s launch post leads with the promise that bots have their own computer. The documentation, last updated the same day, describes a single persistent cloud computer assigned to the user account rather than to any individual bot. Browser cookies and signed-in sessions are shared across the roster, files are visible to every bot, and command-line credentials are shared. One bot can pick up work that another bot saved.
Each bot gets its own screen on that machine, which allows several of them to run browser and desktop tools in parallel. SpaceXAI is direct about what those screens are not. The documentation calls them “separate work surfaces, not separate security boundaries.” It then instructs operators to keep a credential or file off the machine entirely if another bot on the account cannot use it.
The consequences run further than credentials. Signing in for one bot makes that session available to the others because the browser is shared. Installed connectors are account-wide, and their availability is not isolated to a single bot. The shared workspace sits at /workspace and is designed to survive computer updates and recovery, so the durable state is shared across the whole roster.
None of this is an implementation accident. It is what makes handoffs between bots cheap, and cheap handoffs are the product. But an operator reading only the launch page would build a mental model that the documentation contradicts, and that gap is where the risk sits.
Hermes gives each bot its own profile
Nous took the opposite architectural position. In Hermes, a bot is a profile, and each profile has its own configuration, memory, skills, credentials, and chat history stored in its own directory on disk. Handoffs between bots run as real invocations against the named profile, rather than as a shared context blob passed around within a single process.
Nous shipped the teammate protocol as part of v0.20.3, alongside the MCP 2.x SDK migration and a set of runtime hardening changes. The company archived the standalone plugin repository once the merge was completed. Bot Mode is on by default, so a Hermes user who updates gets the roster without opting in.
Two qualifications matter before anyone reads that as containment. A separate credential store does not guarantee different credentials, since what ends up in a new profile depends on how the operator created it and what they edited afterward. And every profile still shares the host machine, its operating system user, and its filesystem permissions. What Hermes documents is workstation-level separation of agent state, a meaningfully stronger default than a shared cloud account, but not the same as isolation.
OpenClaw’s sandbox is off by default
OpenClaw documents the most complete boundary of the four. When the sandbox is enabled with the Docker backend, agent tool execution runs inside isolated containers. At the same time, the gateway remains on the host, and the scope can be selected per session, per agent, or shared across agents. Each scope gets its own workspace. Auth material lives per agent under an agent-scoped auth profiles file. Operators can configure network isolation, resource limits, and allow-or-deny tool policies on top of it.
The documented default for that sandbox mode is off. That is a defensible choice for a project most people run on a laptop, where the container overhead buys little against a single-user threat model. The underlying setup behavior deserves more attention. If sandbox prerequisites fail during setup, the script resets sandbox mode to off rather than refusing to start, so an operator who intended isolation and encountered a Docker socket issue ends up running without sandbox isolation. The documentation also warns against mounting the host Docker socket into agent sandbox containers and flags the CLI container’s shared network namespace with the gateway as a trust boundary in its own right.
ClawFleet answers the same question by moving it into the deployment topology. The project documents a wrapper that puts each OpenClaw or Hermes agent in its own Docker container with an isolated filesystem and network. It lists roughly 500 MB of memory per OpenClaw instance and 150 MB per Hermes instance. That cost is why the other three projects make the boundary optional or skip it, and naming the number makes the trade-off legible.
How to choose which bot is right for you
Scenario
Documented fit
Rationale
Persistent work that must continue with the laptop closed
Grok Bot
The only one of the four with a vendor-run always-on cloud computer, at the cost of one shared credential surface for the whole roster
Several agents with genuinely different credential sets on one workstation
Hermes
Per-profile stores are the documented default, and Bot Mode ships on
Untrusted or multi-tenant agent sessions
OpenClaw with sandbox enabled
Per-agent or per-session container scope with configurable network and tool policy, provided the operator turns it on and verifies it
Isolation as the deployment model rather than a runtime setting
ClawFleet
Container per agent with separate filesystem and networking, at a documented memory cost per instance
Each project gives operators different advice
The operational guidance diverges as sharply as the architecture. OpenClaw’s docs read like infrastructure documentation, naming specific hazards such as the Docker socket and the shared network namespace, and telling the operator what not to do. Hermes documents the profile layout and the protocol, then leaves policy to the operator. Grok Bot’s guidance is largely the warning itself, an instruction to treat the account as the boundary and to keep sensitive credentials off the shared machine entirely.
Grok Bot carries a second disclaimer worth reading alongside the first. Sensitive actions route through an approval mechanism. SpaceXAI documents the categories that trigger it, including sending messages, publishing content, purchases and transfers, deleting data, and touching production. Enforcement runs through an LLM classifier. Cursor‘s documentation for that same engine states plainly that the classifier is not a security boundary and can make mistakes. A buyer evaluating the product therefore finds the phrase twice, attached to the two mechanisms they would most reasonably assume protect them.
AI agents still lack identities of their own
Enterprises can adopt any of these four products today and get real work done, and the honest reading is that all four are engineering their boundaries in good faith against different threat models. What none of them provides is an identity for the agent. In every case, the bot borrows the operator’s credentials, whether from a shared cloud browser, a profile directory, or a container volume, and the entire security conversation boils down to how far those borrowed credentials travel.
“There is no primitive to standardize on, so each project has invented a boundary at whatever layer it already controlled, the account, the profile, the runtime, or the container.”
That is why the four answers differ so much. There is no primitive to standardize on, so each project has invented a boundary at whatever layer it already controlled: the account, the profile, the runtime, or the container. Expect to see that gap close on the identity side rather than the agent side, through scoped delegation and per-agent credentials issued by the identity provider, rather than being copied from the human. Until then, the useful move for platform teams is unglamorous and specific. Read the security page before the launch page, because for this class of product, they describe different things.
If you’ve searched “Abacus.AI” recently, you’ve probably landed on a review that covers one or two products and leaves you wondering how everything fits together. That’s the gap this guide fills. Abacus.AI does not consist of a single chatbot; instead, it’s an ecosystem of products which include personal autonomous agents, multilayered chat app, AI code […]
J&T Global Express has expanded automated sortation across its express network to 435 sets of automated sorting machines, adding 22 sets in the first half of 2026, while deployment of unmanned delivery vehicles rose 87 percent to more than 1,900 units. J&T Global Express disclosed the figures in its interim results for the six months […]
Video Friday is your weekly selection of awesome robotics videos, collected by your friends at IEEE Spectrum robotics. We also post a weekly calendar of upcoming robotics events for the next few months. Please send us your events for inclusion.
This is very, very cool. But I’m trying to think of what the commercial use case will be, you know? I guess, high speed, incredibly dangerous package delivery to second-floor windows or something...?
Humans have a remarkable ability to perform new physical skills from only one or a few examples. Our latest robot foundation model, GEN-1.5, exhibits the beginnings of that same ability: It can learn a new task in seconds, from a single example, without gradient updates or fine-tuning. It displays broad capabilities across one-shot and few-shots learning from demonstration, as well as zero-shot physical generalization. Although the tasks are simple and short-horizon, this is the first model we know for which one-shot and few-shots learning of physical skills have emerged at scale. We view these results as a significant step toward our mission of building general intelligence for the physical world.
I will make the cautionary point that for many of these “the model figured it out” tasks, the blog post can only say that there was no relevant pretraining data “to the best of our knowledge.”
As a professional bagpiper who definitely pays very close attention to whatever that annoying tapping noise is coming from the back of the band, I can attest to this group of robot drummers being absolutely top-notch.
What does it take for an aerial robot to move through a sequence of arbitrary poses—fast, precisely, and continuously? Rather than teaching the robot a behavior from data, we asked how far a first-principles analytical model could take us. Through a collaboration between the AIMS Group at the Hong Kong Polytechnic University and DRAGON Lab at the University of Tokyo, we developed the first sequential-convex-programming-based trajectory-optimization framework for generalized multirotors, covering both conventional and omnidirectional platforms.
Gravis Robotics brings robotic intelligence to heavy construction machines. Our retrofit kit, the Gravis Rack, turns off-the-shelf hydraulic machines into robots. Cameras, lidar, and onboard compute lets your machine see and understand its surroundings, and learning-based control lets it work close to its limits, moving more dirt with full, fast cycles.
Robust brachiation requires precise hand movements to grasp and release bars together with highly coordinated whole-body motion. To address this challenge, we propose a learning-based framework centered on waypoint-guided reinforcement learning (WGRL). WGRL guides the end effector through waypoints while allowing RL to explore and generate dynamic whole-body behaviors. With this approach, the learned policy demonstrated robust brachiation across diverse courses with different bar heights, spacings, and orientations in sim-to-sim experiments. In the real world, our life-size dual-arm robot successfully traversed four consecutive bars.
This work introduces a novel approach to physical human-robot interaction (pHRI) by leveraging the joint torque sensors of standard collaborative robots. By mounting a passive, uninstrumented plexiglass touchpad to the robot’s flange, we transform the robot into a handwriting-based input interface.
The massive growth of generative AI has fundamentally altered data center design. As distributed model training scales to span hundreds of thousands of GPUs,...
The massive growth of generative AI has fundamentally altered data center design. As distributed model training scales to span hundreds of thousands of GPUs, the scale-out network connecting these nodes has emerged as a first-order performance bottleneck. For decades, traditional off-the-shelf Ethernet has been the undisputed king of enterprise and cloud networking. It is cheap, standardized…
Solar panel cleaning robots are often judged by how much dust they can remove in one pass. That matters, but it is not the whole engineering question. The brush roller is the component that repeatedly meets the module surface, so its design has to balance cleaning action with controlled contact, serviceability, and the cleaning limits […]
AI agents have expanded inference from single-turn interactions into multi-step workflows that reason, invoke tools, coordinate subagents, and carry growing...
AI agents have expanded inference from single-turn interactions into multi-step workflows that reason, invoke tools, coordinate subagents, and carry growing context from one turn to the next. The scale of this shift is now visible in raw consumption: across 100 trillion tokens of real-world usage, OpenRouter’s State of AI report found that average prompt tokens per request grew roughly fourfold…
Most LLM inference runtimes have no idea a physical deadline exists. This one refuses admission rather than miss a 33ms robot control cycle, evicts KV cache by meaning instead of age, and is written entirely in hand-written CUDA — no cuBLAS, no libtorch.
Traditional cloud infrastructure was designed for predictable, general-purpose workloads and standard interfaces. Agentic AI factories connect diverse users,...
Traditional cloud infrastructure was designed for predictable, general-purpose workloads and standard interfaces. Agentic AI factories connect diverse users, agents, applications, data sources, and storage systems to massively accelerated compute at multi-terabit bandwidth per server, making dedicated DPU processing essential for line-rate networking, storage, and security.
AI factories are interconnected systems where fleet economics depend on how efficiently the entire stack converts power and capital into completed agent tasks....
AI factories are interconnected systems where fleet economics depend on how efficiently the entire stack converts power and capital into completed agent tasks. While GPUs run the models, CPUs handle orchestration, tool execution, and sandboxed computation. Unlike conventional computing with stable runtime profiles, agentic workloads are unpredictable and highly variable. Based on telemetry from…
NVIDIA Groq 3 LPX is the interactive AI inference accelerator for the NVIDIA Vera Rubin platform. At the core of the platform is NVIDIA Vera Rubin NVL72, the...
NVIDIA Groq 3 LPX is the interactive AI inference accelerator for the NVIDIA Vera Rubin platform. At the core of the platform is NVIDIA Vera Rubin NVL72, the most versatile machine ever built, delivering high throughput and interactivity across the widest range of AI workloads—from small to large models, both open and closed. Groq 3 LPX, when paired with Vera Rubin NVL72, extends the platform’s…
Login
