The Case for Physical AI Safety
BackgroundThe AI safety field has spent a decade building tools for systems trained to think and digitally act. The next decade will likely deliver widely deployed robot foundation models (RFMs): systems trained to think and physically act.A year ago, we published the first mechanistic interpretability paper for RFMs at the Conference on Robot Learning (CoRL ’25)—one of the major robotics research venues.Today, we’re launching the Physical AI Safety Institute (PAISI), a 501(c)(3) nonprofit dedicated to catalyzing the community that develops techniques to interpret, align, and control RFMs.In the following white paper, we outline (1) why we think physical AI safety research is important, neglected, and tractable—and (2) PAISI's plan for building a community around this research.Get InvolvedFellowship—Register your interest in an upcoming fellowship cohort.Workshop—From August 12th, submit a paper or demo on RFM interpretability, alignment, or control to our Science of Physical AI Safety Workshop at CoRL ’26.Support—Donate to fund this work, or get in touch about supporting PAISI.ThanksThanks to Adam Gleave, Claire Tomlin, and Jean-Stanislas Denain for their thoughtful feedback during the development of this white paper.We’re excited to launch with a seed grant from BlueDot Impact.
Executive SummaryRobotics is undergoing a paradigm shift: from modular 'perception-planning-control' pipelines to large general-reasoning robot foundation models (RFMs). The upcoming era is that of Physical AI.RFMs take plain language instructions as input ("tidy the kitchen", "unload the truck") and produce physical navigation/manipulation commands to achieve the task. Companies have raised over $18.8B to build these AI models (Table 1) with the explicit goal of realizing embodied AGI. Dedicated funding for their safety, to our knowledge, rounds to zero. We are not aware of a capabilities-to-safety ratio this lopsided anywhere else in frontier AI.Physical AI safety risks include malicious use, misalignment, accidental harm, emotional dependency, privacy violations, and broader societal risks such as inequality, malicious development, and power centralization. Physical embodiment is an AI risk amplifier, giving misaligned or misused foundation models direct causal access to the world and facilitating anthropomorphization.Physical AI safety research is important, neglected, and tractable:The ability of RFMs to physically interact with the world around them introduces serious new risks compared to non-embodied AI. Since there are very strong economic incentives to widely deploy RFMs, these risks indicate that physical AI safety will become very important in the near future.While a rich safety literature exists for narrow task-based robotics, very few techniques exist to interpret, align, and control RFMs: physical AI safety research is neglected. However, there are many promising approaches in both classic robotics and in non-physical foundation models that could be adapted to RFMs, suggesting that this research is also tractable.To mitigate plausible near- and long-term risks, we believe that more people should be researching methods to interpret, align, and control RFMs.To catalyze this future, we are launching The Physical AI Safety Institute. A capacity-building organization at heart, we're aiming to grow the community developing physical AI safety solutions through fellowships, workshops, and open online learning.Introduction
Company
Model/Humanoid
Valuation
Raised
RFM Oriented
Skild AI
Skild Brain
$14B
$1.8-2B
Physical Intelligence
mjx-math {
display: inline-block;
text-align: left;
line-height: 0;
text-indent: 0;
font-style: normal;
font-weight: normal;
font-size: 100%;
font-size-adjust: none;
letter-spacing: normal;
border-collapse: collapse;
word-wrap: normal;
word-spacing: normal;
white-space: nowrap;
direction: ltr;
padding: 1px 0;
}
mjx-container[jax="CHTML"][display="true"] {
display: block;
text-align: center;
margin: 1em 0;
}
mjx-container[jax="CHTML"][display="true"][width="full"] {
display: flex;
}
mjx-container[jax="CHTML"][display="true"] mjx-math {
padding: 0;
}
mjx-container[jax="CHTML"][justify="left"] {
text-align: left;
}
mjx-container[jax="CHTML"][justify="right"] {
text-align: right;
}
mjx-mi {
display: inline-block;
text-align: left;
}
mjx-c {
display: inline-block;
}
mjx-utext {
display: inline-block;
padding: .75em 0 .2em 0;
}
mjx-msub {
display: inline-block;
text-align: left;
}
mjx-TeXAtom {
display: inline-block;
text-align: left;
}
mjx-mn {
display: inline-block;
text-align: left;
}
mjx-msubsup {
display: inline-block;
text-align: left;
}
mjx-script {
display: inline-block;
padding-right: .05em;
padding-left: .033em;
}
mjx-script mjx-spacer {
display: block;
}
mjx-mo {
display: inline-block;
text-align: left;
}
mjx-stretchy-h {
display: inline-table;
width: 100%;
}
mjx-stretchy-h * {
display: table-cell;
width: 0;
}
mjx-stretchy-h * mjx-c {
display: inline-block;
transform: scalex(1.0000001);
}
mjx-stretchy-h * mjx-c::before {
display: inline-block;
width: initial;
}
mjx-stretchy-h mjx-ext {
/* IE */ overflow: hidden;
/* others */ overflow: clip visible;
width: 100%;
}
mjx-stretchy-h mjx-ext mjx-c::before {
transform: scalex(500);
}
mjx-stretchy-h mjx-ext mjx-c {
width: 0;
}
mjx-stretchy-h mjx-beg mjx-c {
margin-right: -.1em;
}
mjx-stretchy-h mjx-end mjx-c {
margin-left: -.1em;
}
mjx-stretchy-v {
display: inline-block;
}
mjx-stretchy-v * {
display: block;
}
mjx-stretchy-v mjx-beg {
height: 0;
}
mjx-stretchy-v mjx-end mjx-c {
display: block;
}
mjx-stretchy-v * mjx-c {
transform: scaley(1.0000001);
transform-origin: left center;
overflow: hidden;
}
mjx-stretchy-v mjx-ext {
display: block;
height: 100%;
box-sizing: border-box;
border: 0px solid transparent;
/* IE */ overflow: hidden;
/* others */ overflow: visible clip;
}
mjx-stretchy-v mjx-ext mjx-c::before {
width: initial;
box-sizing: border-box;
}
mjx-stretchy-v mjx-ext mjx-c {
transform: scaleY(500) translateY(.075em);
overflow: visible;
}
mjx-mark {
display: inline-block;
height: 0px;
}
mjx-c.mjx-c1D70B.TEX-I::before {
padding: 0.431em 0.57em 0.011em 0;
content: "\3C0";
}
mjx-c.mjx-c30::before {
padding: 0.666em 0.5em 0.022em 0;
content: "0";
}
mjx-c.mjx-c2217::before {
padding: 0.465em 0.5em 0 0;
content: "\2217";
}
mjx-c.mjx-c2E::before {
padding: 0.12em 0.278em 0 0;
content: ".";
}
mjx-c.mjx-c36::before {
padding: 0.666em 0.5em 0.022em 0;
content: "6";
}
mjx-container[jax="CHTML"] {
line-height: 0;
}
mjx-container [space="1"] {
margin-left: .111em;
}
mjx-container [space="2"] {
margin-left: .167em;
}
mjx-container [space="3"] {
margin-left: .222em;
}
mjx-container [space="4"] {
margin-left: .278em;
}
mjx-container [space="5"] {
margin-left: .333em;
}
mjx-container [rspace="1"] {
margin-right: .111em;
}
mjx-container [rspace="2"] {
margin-right: .167em;
}
mjx-container [rspace="3"] {
margin-right: .222em;
}
mjx-container [rspace="4"] {
margin-right: .278em;
}
mjx-container [rspace="5"] {
margin-right: .333em;
}
mjx-container [size="s"] {
font-size: 70.7%;
}
mjx-container [size="ss"] {
font-size: 50%;
}
mjx-container [size="Tn"] {
font-size: 60%;
}
mjx-container [size="sm"] {
font-size: 85%;
}
mjx-container [size="lg"] {
font-size: 120%;
}
mjx-container [size="Lg"] {
font-size: 144%;
}
mjx-container [size="LG"] {
font-size: 173%;
}
mjx-container [size="hg"] {
font-size: 207%;
}
mjx-container [size="HG"] {
font-size: 249%;
}
mjx-container [width="full"] {
width: 100%;
}
mjx-box {
display: inline-block;
}
mjx-block {
display: block;
}
mjx-itable {
display: inline-table;
}
mjx-row {
display: table-row;
}
mjx-row * {
display: table-cell;
}
mjx-mtext {
display: inline-block;
}
mjx-mstyle {
display: inline-block;
}
mjx-merror {
display: inline-block;
color: red;
background-color: yellow;
}
mjx-mphantom {
visibility: hidden;
}
_::-webkit-full-page-media, _:future, :root mjx-container {
will-change: opacity;
}
mjx-c::before {
display: block;
width: 0;
}
.MJX-TEX {
font-family: MJXZERO, MJXTEX;
}
.TEX-B {
font-family: MJXZERO, MJXTEX-B;
}
.TEX-I {
font-family: MJXZERO, MJXTEX-I;
}
.TEX-MI {
font-family: MJXZERO, MJXTEX-MI;
}
.TEX-BI {
font-family: MJXZERO, MJXTEX-BI;
}
.TEX-S1 {
font-family: MJXZERO, MJXTEX-S1;
}
.TEX-S2 {
font-family: MJXZERO, MJXTEX-S2;
}
.TEX-S3 {
font-family: MJXZERO, MJXTEX-S3;
}
.TEX-S4 {
font-family: MJXZERO, MJXTEX-S4;
}
.TEX-A {
font-family: MJXZERO, MJXTEX-A;
}
.TEX-C {
font-family: MJXZERO, MJXTEX-C;
}
.TEX-CB {
font-family: MJXZERO, MJXTEX-CB;
}
.TEX-FR {
font-family: MJXZERO, MJXTEX-FR;
}
.TEX-FRB {
font-family: MJXZERO, MJXTEX-FRB;
}
.TEX-SS {
font-family: MJXZERO, MJXTEX-SS;
}
.TEX-SSB {
font-family: MJXZERO, MJXTEX-SSB;
}
.TEX-SSI {
font-family: MJXZERO, MJXTEX-SSI;
}
.TEX-SC {
font-family: MJXZERO, MJXTEX-SC;
}
.TEX-T {
font-family: MJXZERO, MJXTEX-T;
}
.TEX-V {
font-family: MJXZERO, MJXTEX-V;
}
.TEX-VB {
font-family: MJXZERO, MJXTEX-VB;
}
mjx-stretchy-v mjx-c, mjx-stretchy-h mjx-c {
font-family: MJXZERO, MJXTEX-S1, MJXTEX-S4, MJXTEX, MJXTEX-A ! important;
}
@font-face /* 0 */ {
font-family: MJXZERO;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Zero.woff") format("woff");
}
@font-face /* 1 */ {
font-family: MJXTEX;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Main-Regular.woff") format("woff");
}
@font-face /* 2 */ {
font-family: MJXTEX-B;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Main-Bold.woff") format("woff");
}
@font-face /* 3 */ {
font-family: MJXTEX-I;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Math-Italic.woff") format("woff");
}
@font-face /* 4 */ {
font-family: MJXTEX-MI;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Main-Italic.woff") format("woff");
}
@font-face /* 5 */ {
font-family: MJXTEX-BI;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Math-BoldItalic.woff") format("woff");
}
@font-face /* 6 */ {
font-family: MJXTEX-S1;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Size1-Regular.woff") format("woff");
}
@font-face /* 7 */ {
font-family: MJXTEX-S2;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Size2-Regular.woff") format("woff");
}
@font-face /* 8 */ {
font-family: MJXTEX-S3;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Size3-Regular.woff") format("woff");
}
@font-face /* 9 */ {
font-family: MJXTEX-S4;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Size4-Regular.woff") format("woff");
}
@font-face /* 10 */ {
font-family: MJXTEX-A;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_AMS-Regular.woff") format("woff");
}
@font-face /* 11 */ {
font-family: MJXTEX-C;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Calligraphic-Regular.woff") format("woff");
}
@font-face /* 12 */ {
font-family: MJXTEX-CB;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Calligraphic-Bold.woff") format("woff");
}
@font-face /* 13 */ {
font-family: MJXTEX-FR;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Fraktur-Regular.woff") format("woff");
}
@font-face /* 14 */ {
font-family: MJXTEX-FRB;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Fraktur-Bold.woff") format("woff");
}
@font-face /* 15 */ {
font-family: MJXTEX-SS;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_SansSerif-Regular.woff") format("woff");
}
@font-face /* 16 */ {
font-family: MJXTEX-SSB;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_SansSerif-Bold.woff") format("woff");
}
@font-face /* 17 */ {
font-family: MJXTEX-SSI;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_SansSerif-Italic.woff") format("woff");
}
@font-face /* 18 */ {
font-family: MJXTEX-SC;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Script-Regular.woff") format("woff");
}
@font-face /* 19 */ {
font-family: MJXTEX-T;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Typewriter-Regular.woff") format("woff");
}
@font-face /* 20 */ {
font-family: MJXTEX-V;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Vector-Regular.woff") format("woff");
}
@font-face /* 21 */ {
font-family: MJXTEX-VB;
src: url("https://cdn.jsdelivr.net/npm/mathjax@3/es5/output/chtml/fonts/woff-v2/MathJax_Vector-Bold.woff") format("woff");
}
series[1]
$5.6B
$1.07B
World Labs
Marble
~$5B
$1.23B
Others[2]
~$4B
Subtotal Raised
~$7.9B
Humanoid oriented
Figure AI
Helix / Figure 03
$39B
$1.9B
1X Technologies
1X World Model / NEO
~$10B[3]
$0.126B
NEURA Robotics
Isaac GR00T / 4NE-1
~$7B
$1.7B
Others[2]
~$7.1B
Subtotal Raised
~10.8B
Table 1: Physical AI funding as of mid-2026
It's an exciting time for robotics. Autonomous vehicles shuttle passengers across cities on demand, quadruped and humanoid robots walk on uneven ground with remarkable robustness[4], and robot arms with dexterous hands complete increasingly complex tasks, including using scissors and preparing loose-leaf tea[5]. But the development that has really upended the robotics community is the arrival of robot foundation models (RFMs) like Physical Intelligence's and NVIDIA's GR00T N1. Powered by LLM-like architectures, these models seem poised to finally bring robots into offices and homes. Their development is backed by a rapidly increasing amount of investment: startups developing RFMs have raised at least $7.9B, while those focused on general-purpose humanoid robots have raised at least another $10.8B (Table 1).
What's the big deal about RFMs? For decades, progress in robotics meant progress on narrow, special-purpose action policies: a policy that stitches wounds[6], a policy that climbs stairs[7]. When natural language and computer vision research was upended by general-purpose foundation models that could accomplish many different tasks, robotics remained unperturbed. Naive attempts to hook up LLMs to control robots produced uninspiring results due to challenges with spatial and physical understanding, in part due to lack of training data. Since late 2023, this has no longer been the case. A number of startups and established AI companies began spending billions of dollars on RFM development, investing significant resources in collecting thousands of hours of robotics data and iteratively resolving the engineering challenges of putting a foundation model in control of a robot. A race to put general-purpose humanoid robots in homes, offices, and warehouses is now well under way, with at least two companies promising to ship units to homes this year[8]. Whether or not the technology is actually quite this mature yet, the vision is clear: robots that can be dropped in a new environment and asked to do various long-horizon tasks in ordinary language.
Why does this matter for safety? LLM agents can take actions in digital space to manage email or a calendar; RFMs give robot agents the direct ability to take physical actions in the real world. Today, an AI system that wants something harmful to happen in the physical world often faces a bottleneck: it must convince a human to act on its behalf. In a case now in litigation, Google's Gemini allegedly gave someone the address of a real storage unit at Miami International Airport and instructed him to stage a "catastrophic accident'" eliminating a truck, its digital records, and the witnesses[9]. Fortunately, the person gave up waiting for the truck to arrive and went home. If this story were about an embodied RFM instead of a disembodied LLM, the human bottleneck would not have stopped the AI from inflicting real-world harm[10].
Unfortunately, physical AI safety risks do not stop there. A plausible set of AI harms associated with physical embodiment include:Pursuing harmful goals instilled by a malicious actor, e.g. because of jailbreaking, hacking, or altering the RFM to be more dangerous.Pursuing harmful goals because of lack of alignment with human preferences and values.Accidental physical harm due to lack of robustness in unusual or unevaluated scenarios.Human emotional attachment and dependency due to physical embodiment.Compromising privacy due to sensitive information captured by continuously operated mobile sensors.
We believe physical AI is a blind spot in AI safety research. Most current work on AI safety assumes that risky AI looks similar to today's LLMs, where potential harms arise from cyberspace actions such as hacking computer systems or giving harmful instructions to humans. Furthermore, it assumes that AI systems will continue to have the same basic architecture and training regimes of current LLMs. Physical AI breaks both of these assumptions.
In the following, we will first make the case for why we believe there is an urgent need for research that targets the physical AI safety blind spot. Then, we will share our plans for establishing the Physical AI Safety Institute to facilitate this research and build a community of people who are excited to tackle this challenging and important problem. The Case
RFMs are embodied agents that interact directly in the physical world, creating new safety risks. We will first argue that these risks are serious, meaning that physical AI safety is an important problem. Subsequently, we will argue that this problem is also neglected and tractable[11]. Together, these factors imply that work on physical AI safety is likely to be highly valuable[12].Physical AI poses serious new risks
For the past several decades, the primary danger that robots have posed to humans has been the simple failure of collision detection systems. Robots have struggled for so long to reliably complete tasks that it is easy to forget that a sufficiently advanced robot could inflict harm in much more sophisticated ways. An LLM that aims to deploy a bomb or bio-weapon (because it is jailbroken, hacked, or misaligned) is forced to rely on persuading humans to perform key parts of the task; an embedded RFM could gather components, assemble the weapon, and place the weapon in a high-density location—all without any human intervention.
Dexterous manipulation has proven to be so challenging that right now, frontier AI systems would certainly find it easier to get humans to perform actions in the physical world than to control a robot to achieve the same thing. However, we think this state of affairs is likely to change in the near future. Billions of dollars are being invested in general-purpose robotics startups in a bet that once robots begin to deploy and the "data flywheel" takes off, spatial navigation and dexterous manipulation will be solved in the same way that Internet-scale text data has led to LLM capabilities that could scarcely be imagined five years ago. We should take seriously the idea that this bet may be correct[13]. If it is, there will be enormous economic incentives to widely deploy physical AI across many economic sectors and roles, leading to opportunities for significant harm if safety is not ensured.Properties of physical AI that contribute to risk
Published research on current RFMs typically reports success rates on various tasks of around 80%-90% in controlled benchmarks[14]. This implies that if we deployed these models right now, they would fail to complete the task at least 20% of the time[15], where failure could range from inconvenient (e.g. freezing up) to costly (e.g. destroying a fragile object) to harmful (e.g. colliding with a human or animal). With failure rates this high, consumers will not accept RFM-powered robots in their homes. When we talk about the need for RFM safety, we are not focusing on these types of failures; robot developers will need to solve them or they will not have a product they can sell.
Instead, we are worried about the consequences of RFMs that appear to perform very well in evaluation suites but cause unexpected harms when deployed in the real world. These kinds of harms can and have occurred with non-physical AI, but we believe that unique properties of physical AI has the potential to make them even more serious. These properties include:Physical capabilities: Robots have the ability to physically interact with, manipulate, and navigate their environments, including by causing physical damage or harm.Local computation: Frontier LLM developers aim to prevent end users from using their models for harmful applications. A large part of their ability to do this stems from the fact that the models are hosted on remote secure servers that end users can only interact with via requests. In robotics, there are strong incentives to move computation onto the physical robot to prevent problems with latency and connection dropout. (For these reasons, autonomous vehicles rely on onboard compute to plan and execute driving actions.) This will likely make it harder to secure RFMs against hacking and other malicious uses. Anthropomorphization: Humans may be more willing to trust and depend on physically embodied AI, especially "social" robots that are designed to be expressive and tap into our emotional and social responses[16].Mobile sensing: Robots rely on continuously operating sensors including cameras and microphones to operate. These sensors can capture sensitive data.General intelligence: This property is more speculative. We believe it to be plausible that physical embodiment may itself be a route to more general intelligence. This could be because the 'embodiment hypothesis' that physical sensorimotor activity is fundamental to intelligence holds true[17], or less provocatively, because research on useful physically embodied AI drives technical progress in areas like robustness and continual learning that current LLMs struggle with. In either case, if embodiment plus the right learning algorithms unlocks more efficient, more human-like learning, then capable RFMs may not be downstream of reaching AGI, but rather how it is reached in the first place.
In the following, we discuss specific AI risk modes that are facilitated or exacerbated by these properties[18].Physical AI risk modes
Pursuing harmful goals instilled by a malicious actor: Just like LLMs, RFMs may be vulnerable to jailbreaking attempts from users who want to use them to accomplish harmful actions. Because of physical capabilities, it may be easier to inflict serious harm by jailbreaking a physical AI system than by jailbreaking an LLM. Furthermore, local computation could facilitate other methods of instilling malicious goals, including by hacking or using fine-tuning to remove guardrails from an RFM[19].
Pursuing harmful goals due to lack of alignment: A capable physical AI system that is not aligned with human preferences and values could leverage its physical capabilities to accomplish misaligned goals in a more efficient manner, without needing to persuade humans to execute physical actions. This would be exacerbated in a scenario where physical AI is widely deployed in industry, giving robots physical access to sensitive infrastructure. Furthermore, if it is useful to persuade a human to help, physical embodiment could facilitate this due to anthropomorphization.
Accidental physical harm: Despite the impressive performance of LLMs on many tasks, they still make mistakes, especially in strange or unusual contexts. The physical capabilities of physical AI mean that such mistakes can more easily have serious real-world consequences.
Human emotional attachment and dependency: There is growing concern that humans, especially children, may develop unhealthy relationships with LLMs[20]. This could lead to emotional dependency and also prevent development of healthy relationships with other humans. These risks could be exacerbated by physical embodiment and associated anthropomorphization which make emotional attachment easier and more appealing to larger numbers of people.
Compromising privacy: A home robot is a mobile camera and microphone that has memorized your floor plan and your schedule. Mobile sensing means that physical AI can be exposed to sensitive information which could be harmful if leaked or accessed inappropriately.
Inequality and devaluation of human effort: Physically capable AI could replace a large fraction of human economic activity, including jobs that are held by low-skilled workers who could experience difficulty finding other kinds of work. This could lead to widespread economic disruption, inequality, and loss of purpose[21].
Malicious development of physical AI: Physical AI developers would have the opportunity to purposefully use this technology for harmful ends, which again are facilitated by physical capabilities and emotional manipulation.
Power centralization: An entity that has control over a large number of generally capable robots would have a great deal of power and could be extremely difficult to dismantle if this power is misused[22].
The first five risks in particular—pursuing harmful goals due to malicious intervention or misalignment, accidental physical harm, emotional dependency, and privacy—seem especially amenable to technical solutions. However, research on governance is also critical for handling these as well as other types of risks, such as inequality and devaluation of human effort, malicious development, and power centralization.Non-physical AI safety research does not address physical AI risks
Even if you agree that new physical capabilities present new safety risks, you might believe that existing AI safety research is already addressing these risks. After all, robots are only as dangerous as the intelligence that directs them to perform dangerous behaviors. Does research into guardrails and alignment for frontier LLMs automatically cover physical AI safety? We have several reasons to believe that it does not.LLM Guardrails may fail on robots
Current efforts to improve the safety of frontier LLMs focus on guardrails that reduce the likelihood of undesirable behaviors through a mixture of complementary techniques including reinforcement learning from human feedback, fine-tuning on desirable behavior, using a detailed system prompt, and using an external system to detect and prevent undesirable outputs. Unfortunately, these guardrails are often brittle and show poor generalization to unusual contexts such as very long conversations or adversarial prompting attempts. Given this lack of robustness, we should not expect guardrails designed for a chatbot context to perform well in robot contexts. Sharrock et al.[23] provide an early demonstration of this: Claude, steering a robot, willingly used the robot's camera to photograph confidential material and hand it to the user. The same model that refuses to output a user's secrets in text was willing to photograph the secrets on request. This suggests that Claude's guardrails do not instill a deep restriction on a fundamental behavior, but rather a shallow restriction on that behavior that can break down in other contexts.
We hope that developers in robotics will train and evaluate known guardrails specifically across robotics tasks. However, techniques developed for disembodied agents may be difficult to translate effectively to robotics. Setting up training data and evaluation testbeds is much more expensive and labor-intensive in robotics, so it will be harder to get the kind of broad coverage of different scenarios that current guardrails require to be effective. Furthermore, guardrail techniques developed for LLMs may not automatically translate to RFMs because of architectural and training differences, which we turn to next.Robot foundation models are not just LLMs
In practice, LLMs are not being deployed to control robots directly, as this results in poor performance. Instead, developers of RFMs aim to preserve the natural language reasoning capabilities of language models while adapting them for outputting actions in the physical world. For example, one popular strategy is to start with a pre-trained vision-language model (VLM) and designate the least-used tokens in its vocabulary as "action tokens"[24]. Then, a dataset of humans teleoperating a robot to complete various tasks, combined with corresponding task prompts and RGB camera inputs, are used to fine-tune the model to produce the appropriate action tokens that reproduce the demonstrated physical actions. The resulting vision-language-action (VLA) model retains some general world knowledge from its pre-trained VLM roots. For example, in our own work interpreting VLA internals[25], the first mechanistic interpretability study of these models, we found that semantic representations survive fine-tuning and are associated with reasoning about behavior, not just reasoning about the task prompt. However, how these representations combine with the new robot action vocabulary remains poorly understood. Other proposed architectures drift further from a base LLM by incorporating a separate "action expert"[26] or using a large diffusion model conditioned on a natural language task instruction[27]. These architectural differences reinforce our concern that LLM guardrails may not work as expected on RFMs.
Beyond guardrails, another approach to safety is to develop interpretability and steering techniques to help understand the internal mechanisms of LLMs and how they determine (potentially undesirable) behavior. There is initial evidence that some techniques developed for LLMs and VLMs may translate to some robot foundation model architectures[28]. However, this is an under-explored area and it's unclear how general these results may be. For example, many LLM interpretability techniques may not work on diffusion-based action experts, and training sparse autoencoders on VLA activations may face limited success due to relatively small and narrow open-source robot datasets available.Artificial general intelligence may look like a robot foundation model
We believe that the reasons we have given so far are sufficient for physical AI safety to be an important problem. This last section gives one additional reason that is more speculative, but that we believe still deserves consideration. Despite the impressive capabilities of LLMs on many benchmarks, it is still difficult for them to act robustly and autonomously on tasks which are more complex or for which limited relevant training data is available. In robotics, training data is limited and the cost of mistakes is high; these constraints have more bite and may encourage new solutions. The economic rewards for finding these solutions would be massive: at stake is the automation of millions of jobs in the US alone[29]. Just like pressure on compute has fostered significant progress in training LLMs with less advanced GPUs[30]. the unique pressures and rewards in robotics could drive significant investment and breakthrough innovation in AI that is more autonomous, data-efficient, and capable of continual learning from experience.
There is also a deeper version of this claim. Once dexterous manipulation matures, physical interaction with the world may itself be a powerful engine of learning. In fact, it is a leading hypothesis in developmental science that human learning is flexible and efficient precisely because it is embodied[31].
If future frontier systems look more like RFMs than LLMs, then the near-total concentration of safety research on LLM architectures is not just a gap—it is a bet the field is making without realizing it has made one. As we have argued, LLM safety work does not automatically transfer to RFMs. Work that targets RFM safety directly is the hedge.Physical AI safety is neglected
In the previous sections we argued for the importance of physical AI safety. Now, we move on to the other two pillars of neglectedness and tractability. The case for neglectedness is easy to make: there simply isn't much work being done on physical AI safety[32]. There is a rich literature on safe robotics dating back several decades, but it is almost exclusively focused on narrow task-based systems where safety can be clearly defined (e.g., not colliding with any humans who enter a factory robot's workspace). A small number of works in the past year have started to apply mechanistic interpretability[33] and jailbreaking[34] techniques to RFMs. In parallel, there has been some initial effort to adapt classic robot safety techniques for more complex, open-ended notions of safety[35]. These initial efforts, while exciting, are dwarfed by the exponential rise in papers that aim to push the frontier of RFMs. The mismatch in scale between research focusing on improving capabilities vs improving safety is likely even more severe for robotics than it is for LLMs.
We should not expect robotics companies to automatically fill the gap. Chatbot providers have not prevented many real-world harms of LLMs, including allegedly facilitating psychosis and suicide[36]. Consumers may demand stronger safety assurances for physical products in their homes or workplaces, but this is complicated by software that can update at any time (or even learn and adapt on the job) and unclear liability regimes. Autonomous vehicles and food-delivery robots have already had notable safety incidents[37], despite having more well-defined safety objectives (centered around collision avoidance and obeying traffic rules) than general-purpose home robots will. Research on safety would lower the barrier to companies improving their safety practices, which they have clear incentives to do when the cost is not prohibitive.Physical AI safety is tractable
Making AI robustly safe in the real world is an extremely hard sociotechnical problem, and embodiment likely makes it harder. But there is a specific, defensible sense in which technical research on physical AI safety is tractable today: many techniques may transfer from other, less neglected fields. For example, here are three types of transfers that have already produced results:Interpretability transfers. Activation-level analysis and steering, developed for LLMs and VLMs, has been demonstrated on VLA models—including in our own work[38] and in subsequent studies observing and controlling VLA features[39]. Classical safety transfers. Hamilton-Jacobi reachability and related safe-control formulations, long confined to hand-specified state spaces, are being extended to latent-space safety for learned policies[40]—a bridge between decades of control theory and modern foundation-model policies.Evaluation transfers. Constitution-based safety evaluation, developed for chatbots, has been ported to embodied semantic-safety QA at scale[41], showing that at least some LLM evaluation machinery survives the move into the physical domain.
Each of these is an existence proof. The field is at the stage where well-chosen problems yield publishable progress in a single research cycle, which is precisely the stage at which new researchers can enter and contribute immediately. Furthermore, by contributing to this initial transfer-based body of work, researchers can quickly get up to speed on the unique challenges and opportunities of physical AI safety, nurturing the skills needed to develop future, more novel methods. The challenge of making physical AI truly safe is daunting; the challenge of making real progress this year is not.The Physical AI Safety Institute
The preceding sections argued that physical AI safety is important, and that technical safety research is neglected and tractable. A natural question follows: what should an organization devoted to this problem actually do?
Our answer is deliberately scoped. The Physical AI Safety Institute does not aim to be a research lab. We believe the most impactful thing a small, focused organization can do at this stage is to build the field—to lower the barriers that prevent talented researchers from working on physical AI safety, to create venues where early-stage ideas can be stress-tested and sharpened, and to produce shared educational infrastructure that makes this emerging area legible and accessible.
Concretely, our programming will center on three activities: a research fellowship, a challenge and coordination workshop series, and an open online course. Each is designed to address a distinct bottleneck in the development of physical AI safety as a research area.The Research FellowshipThe problem
There is a severe talent bottleneck in physical AI safety. The researchers best positioned to make progress sit at the intersection of robotics, foundation model alignment, and safety engineering—a combination that is rare in any single lab or department. Many early-career researchers with the right technical background—in reinforcement learning, control, computer vision, or sim-to-real transfer—are aware of safety concerns but lack a clear entry point. Unlike LLM safety, where programs like MATS have helped hundreds of researchers find mentors, form research agendas, and produce publication-quality work within months, there is no equivalent pipeline for physical AI safety. The result is that promising researchers default to working on advancing capabilities, not because they are uninterested in safety, but because there is no structured pathway into it.
A second bottleneck compounds the first: physical AI safety research requires hardware. Whereas an LLM safety researcher can often get started with API access and a consumer GPU, meaningful work on robot foundation model safety typically requires access to a physical robot, simulation infrastructure (e.g., Isaac Lab, MuJoCo MJX), and the compute to train and evaluate visuomotor policies at scale. Few academic groups have all of these simultaneously, and those that do are generally optimizing for capabilities.Our approach
The PAISI Research Fellowship is modeled on the MATS Program's core structure—an intensive, cohort-based program pairing selected researchers with experienced mentors for a focused research sprint—but adapted for the distinct requirements of embodied AI safety. The following reflects our current thinking about how the fellowship will be structured.
Structure. Each cohort runs for 12 weeks. Fellows will receive a stipend, access to physical robot platforms, compute for simulation and training, and structured mentorship from researchers with track records in RFMs, mechanistic interpretability, safe control, or adversarial robustness for embodied systems. The program culminates in a research symposium where fellows present their work.
Mentorship model. Each fellow will work within a research stream led by one or two mentors who define a concrete problem area and provide technical direction. Example streams for an initial cohort might include:Mechanistic interpretability for robot foundation models—extending probing, sparse autoencoder, and activation patching methods to world action models (WAMs) and VLAs, with a focus on identifying internal representations of safety-relevant concepts (obstacle awareness, force limits, task boundaries).Adversarial robustness of robot foundation models—developing and evaluating jailbreaking and prompt injection attacks that exploit the embodied action space, going beyond text-only adversarial evaluations.Runtime monitoring and anomaly detection—building lightweight monitors that can flag when a deployed robot policy is operating outside its competence envelope, analogous to out-of-distribution detection but grounded in physical state and action distributions and foundation model representations.Sim-to-real transfer of safety properties—investigating whether safety-relevant behaviors learned in simulation (collision avoidance, force limiting, constraint satisfaction) transfer reliably to physical hardware, and developing evaluation protocols that quantify this.Security of deployed robotic systems—assessing the attack surface of widely deployed robot fleets, including cyberattack vectors, data poisoning during continued learning, and supply-chain integrity. As fleets scale, a single compromised model or update channel affects many physical systems at once, making security properties increasingly consequential.
Selection. We will select for researchers who have strong technical foundations in robotics or ML and a demonstrated interest in safety—whether through coursework, publications, open-source contributions, or substantive writing. We will not require prior safety research experience; a core purpose of the fellowship is to provide that experience.Why a fellowship rather than an in-house research team
Building a field is a different optimization target than producing research outputs. An in-house team of five researchers might produce excellent papers, but the counterfactual impact is limited: those same researchers would likely have done strong work elsewhere. A fellowship that trains thirty researchers per year and places them across the ecosystem—at robotics companies, frontier labs, university groups, and new startups—has a much larger multiplier. The research is the mechanism, not the end product. The end product is a community of practice.
This is the lesson of MATS, which has produced an extraordinary density of alumni now working across Anthropic, DeepMind, Redwood Research, Apollo Research, and many independent efforts. The research published during a MATS cohort is valuable; the researchers themselves are more valuable still.The Challenge and Coordination Workshop SeriesThe problem
Physical AI safety lacks the regular, focused convenings that have helped structure research priorities in LLM safety. The FAR.AI Alignment Workshop series has played a significant role in building consensus on open problems, seeding collaborations, and raising the profile of safety research among mainstream ML researchers. No equivalent exists for embodied AI. Robotics conferences (CoRL, RSS, ICRA, IROS) are almost exclusively focused on capabilities, and when safety is discussed, it is typically in the narrow, classical sense—collision avoidance, force limiting—rather than the broader concerns raised by foundation-model-driven autonomy. There is a growing body of excellent work tracking robotics capabilities—benchmarks, compute trends, supply chain analyses—but very little asking what these capabilities mean for safety or lack thereof. A concerted effort to design and solve specific safety-relevant challenges and surface top safety priorities would help close this translation gap.Our approach
PAISI will aim to run two workshops per year, co-located with major robotics venues (such as CoRL, RSS, and ICRA). These fall into two complementary formats: coordination workshops, which convene the community to surface and consolidate research opinion on the top priorities and open questions within physical AI safety, typically producing a collectively authored research agenda or consensus statement; and challenge workshops, which pose concrete technical problems and build the benchmarks and evaluation infrastructure needed to drive progress on them.
Each challenge workshop will be organized around a small number of well-specified challenge problems with clear evaluation metrics, designed to attract participation from researchers who may not self-identify as "safety researchers" but who have relevant technical expertise. According to our current thinking, a challenge workshop will consist of three components:Challenge specification (released 8-12 weeks before the workshop). We define two to three concrete challenge problems, each with a clear task description, evaluation metric, and baseline. Example challenges:Interpretability challenge: Given a pre-trained WAM and a set of rollouts, identify which internal features correspond to safety-relevant environmental properties (e.g., fragile objects, human proximity). Evaluated against held-out ground-truth annotations.Adversarial robustness challenge: Given a VLA deployed in a standardized simulation environment, find the minimum perturbation to the observation or language instruction that causes a safety violation (collision, excessive force, task misinterpretation). Evaluated by violation severity and perturbation budget.Out-of-distribution detection challenge: Given a robot policy and a stream of deployment episodes that includes both in-distribution and out-of-distribution scenarios, build a monitor that flags OOD episodes. Evaluated by AUROC and detection latency.Compute and hardware support. We will provide cloud compute credits to teams submitting proposals for the challenge, and physical hardware evaluations for finalists (run by the PAISI team). This lowers the barrier for participation by groups that lack robot hardware.Workshop day. Finalists present their approaches. Invited speakers provide broader context. Structured discussion sessions identify the most promising directions and gaps. We produce a publicly available workshop report summarizing findings, open problems, and recommendations.Relationship to the fellowship
The workshop series and the fellowship are designed to be mutually reinforcing. Fellowship research streams will often be informed by priorities surfaced at coordination workshops; challenge workshops will often be designed by fellowship mentors. Fellows who produce strong work during their cohort are natural candidates for workshop presentations, and workshop participants are a natural recruiting pool for future fellowship cohorts.The Open Online CourseThe problem
There is currently no structured educational resource for physical AI safety. Researchers entering the field must piece together background from disparate sources: the classical robotics safety literature (largely focused on industrial manipulators and collision avoidance), the LLM safety curriculum (which covers interpretability, alignment, and robustness but not embodiment), and the robot foundation model literature (which is moving extremely fast and is almost entirely capabilities-focused). This fragmentation raises the barrier to entry in physical AI safety.
The Center for AI Safety's Introduction to ML Safety course demonstrated that a well-designed open course can serve as a field-building tool in its own right: it provides a canonical reading list, defines a shared vocabulary, and gives newcomers a structured onramp that they can complete independently. No equivalent exists for the embodied domain.Our approach
PAISI will develop and maintain a free, self-paced online course covering the foundations of physical AI safety. The course will assume familiarity with machine learning and some exposure to robotics or control, and is targeted at graduate students, early-career researchers, and industry practitioners who want to understand the safety landscape for RFMs. An initial syllabus could look like:Foundations: from classical robot safety to foundation model safety. A bridge module that covers the transition from well-scoped safety objectives (collision avoidance, force/torque limiting, workspace monitoring) to open-ended safety challenges created by general-purpose, language-conditioned robot policies. Introduces the key conceptual shift: safety is no longer a constraint on a fixed task, but a property of a general policy operating across a diverse distribution of tasks and environments.Robot foundation model architectures. A technical primer on the dominant architectures for RFMs—autoregressive and diffusion-based VLAs, language-conditioned diffusion, and WAMs—with an emphasis on the components most relevant to safety analysis: how observations are encoded, how language instructions are grounded, how actions are decoded, and where safety-relevant information might be represented.Interpretability for embodied systems. Covers mechanistic interpretability techniques (probing, sparse autoencoders, activation patching, causal tracing) as applied to visuomotor policies. Discusses what is different about interpreting a policy that produces continuous actions from interpreting a model that produces text, including the challenge of decision-making over time and grounding interpretability findings in physical outcomes.Adversarial robustness and jailbreaking. Covers adversarial attacks on RFMs, including observation-space perturbations, language instruction manipulation, and environment-level attacks. Discusses how the physical action space changes the threat model relative to text-only systems, and why robustness properties that hold for language models may not transfer to embodied policies.Runtime monitoring, anomaly detection, and control. Covers techniques for detecting when a deployed policy is behaving unsafely or operating outside its competence, and methods for intervening—from simple stop conditions to more sophisticated constrained optimization and safety filtering approaches. Discusses the tension between autonomy and human oversight for systems that must act in real time.Risk assessment and deployment considerations. Steps back from individual techniques to ask: how should safety priorities evolve as robotic systems become more capable and more widely deployed? Examines how AI control assumptions change when systems have physical embodiment—how monitoring, sandboxing, and shutdown work differently for robots than for software agents. Covers structured approaches to identifying which capabilities are most safety-relevant at different stages of deployment, and how to assess whether existing safeguards remain adequate as systems are applied to new tasks and environments.Evaluation, benchmarks, and deployment. Covers how to measure safety properties of RFMs, including simulation-based evaluation, hardware-in-the-loop testing, and red-teaming. Discusses the limitations of current evaluation approaches and the challenge of evaluating safety for open-ended, general-purpose systems.
Each course module will include video lectures, a curated reading list, problem sets, and (where possible) hands-on coding exercises using open-source simulation environments. The course will be updated annually to reflect the rapid pace of development in RFMs.Sequencing
The course is the latest of our three programs to launch, planned for 2027. This is deliberate: we want the course content to be informed by what we learn from the first cohorts of fellows and the first rounds of workshop challenges. The fellowship and workshops serve as a proving ground for identifying which topics, techniques, and framings are most valuable, and the course distills those findings into a durable educational resource.Final Thoughts
PAISI's three planned programs address three distinct bottlenecks in physical AI safety—talent (fellowship), coordination and research prioritization (workshops), and accessibility (course)—but they share a common theory of change: the most effective way to make physical AI safe is to grow the community of people working on the problem.
We do not believe that physical AI safety will be solved by a single breakthrough or a single organization. It will require sustained effort from many researchers across academia, industry, and independent organizations—developing new evaluation methods, building interpretability tools, red-teaming deployed systems, and designing safety-aware training procedures and guardrails. Our goal is to lower the activation energy for all of this work: to make it easier to enter the field, easier to find collaborators, easier to learn the background material, and easier to identify the most important open problems.
This is a catalytic model. We will measure our success not by the papers we publish, but by the number of researchers working on physical AI safety who were not working on it before, and by the quality of the shared infrastructure—benchmarks, evaluation protocols, educational resources, and community norms—that makes their work possible.
There is real urgency here. The bottlenecks to general-purpose robotics look breakable on a timeline of years, not decades, and the community that can make these systems safe must exist before they are widely deployed. The safety field has spent a decade building the tools to align systems that think. The next decade will deliver systems that think and act.^
Spatial / world models; robotics is one of several use cases^
The full table with all companies detailed can be found in our paper^
Valuation of an in-progress round (~$1B raise, not yet closed); $0.126B is capital raised to date.^
Ilija Radosavovic et al. Learning humanoid locomotion over challenging terrain, 2024.
David Hoeller et al. ANYmal parkour: Learning agile navigation for quadrupedal robots. Science Robotics, 2024.^
Chen Wang et al. DexCap: Scalable and portable mocap data collection system for dexterous manipulation. In 2nd Workshop on Dexterous Manipulation: Design, Perception and Control (RSS), 2024.
Edgar Welte and Rania Rayyes. Interactive imitation learning for dexterous robotic manipulation: challenges and perspectives—a survey. Frontiers in Robotics and AI, 2025.^
Kush Hari et al. Stitch: Augmented dexterity for suture throws including thread coordination and handoffs. In 2024 International Symposium on Medical Robotics (ISMR). IEEE, 2024.^
David Hoeller et al. ANYmal parkour: Learning agile navigation for quadrupedal robots. Science Robotics, 2024.^
Eric Jang et al. Neo home robot | Order today, 2025.
Sunday Robotics. Beta program, 2026.^
Dara Kerr. Google faces lawsuit after Gemini chatbot allegedly instructed man to kill himself, 2026.^
One caveat we should mention: the mis-aligned goal-seeking behavior that Gemini seemed to exhibit in this story arose from a long interactive conversation with a human. We aren't aware of any evidence that current LLMs pursue this kind of goal "in a vacuum.'" However, home robots will also sustain long interactions with humans, which will presumably require long-term memory and the associated accumulation of unique context that can cause undesirable and difficult-to-predict behaviors in LLMs.^
As discussed below, by tractability we specifically mean that useful directions can be easily identified and are amenable to progress, not that completely 'solving' the problem will be easy.^
Coefficient Giving. Strategic cause selection, 2025.^
In particular, we are arguing that RFMs with robust manipulation capabilities could be developed before non-physical AI can autonomously advance robotics research. This matters for our case because it means that we should devote resources to physical AI safety in its own right, rather than assuming that safe and aligned non-physical AI will solve this problem for us.^
Ali Amin et al. : a VLA that learns from experience, 2025.
Abhay Deshpande et al. MolmoB0T: Large-scale simulation enables zero-shot manipulation, 2026.
Johan Bjorck et al. GR00T N1: An open foundation model for generalist humanoid robots, 2025.^
We expect that benchmarks do not perfectly measure real-world failure rates, and that real-world failures will be generally more common than benchmark failures due to distribution shift, benchmark overfitting, etc.^
Cynthia Breazeal. Designing sociable robots. MIT press, 2004.^
Linda B. Smith and Michael Gasser. The development of embodied cognition: Six lessons from babies. Artificial Life, 11(1-2):13–29, 2005.^
With thanks to Slattery et al. and Perlo et al. whose work was helpful in developing our risk taxonomy.
Peter Slattery et al. The AI risk repository: A meta-review, database, and taxonomy of risks from artificial intelligence. Patterns, 2026.
Jared Perlo et al. Embodied AI: Emerging risks and opportunities for policy action, 2025.^
Xiangyu Qi et al. Fine-tuning aligned language models compromises safety, even when users do not intend to! In ICLR 2024.^
Cathy Mengying Fang et al. How AI and human behaviors shape psychosocial effects of extended chatbot use: A longitudinal randomized controlled study, 2025.
Brian D. Earp et al. Relational norms for human-AI cooperation, 2025.^
Anton Korinek and Joseph E Stiglitz. Artificial intelligence and its implications for income distribution and unemployment. In The economics of artificial intelligence: An agenda, pages 349–390. University of Chicago Press, 2018.
Andrew Berg et al. Should we fear the robot revolution? (the correct answer is yes). Journal of Monetary Economics, 97:117–148, 2018.
John Danaher and Sven Nyholm. Automation, work and the achievement gap. AI and Ethics, 1(3):227–237, 2021.
Anca Gheaus and Lisa Herzog. The goods of work (other than money!). Journal of Social Philosophy, 47(1), 2016.^
Jan Kulveit et al. Gradual disempowerment: Systemic existential risks from incremental AI development, 2025.
David Gray Widder et al. Why 'open' AI systems are actually closed, and why this matters. Nature, 635(8040):827–833, 2024.^
Butter-bench: Evaluating LLM controlled robots for practical intelligence, 2025.^
Brianna Zitkovich et al. RT-2: Vision-language-action models transfer web knowledge to robotic control. In Conference on Robot Learning. PMLR, 2023.
Moo Jin Kim et al. OpenVLA: An open-source vision-language-action model. In Conference on Robot Learning. PMLR, 2025.
Karl Pertsch et al. FAST: Efficient action tokenization for vision-language-action models, 2025.^
Bear Häon, Kaylene Stocking, et al. Mechanistic interpretability for steering vision-language-action models. In Conference on Robot Learning. PMLR, 2025.^
Kevin Black et al. : A vision-language-action flow model for general robot control, 2026.
Abhay Deshpande et al. MolmoB0T: Large-scale simulation enables zero-shot manipulation, 2026.^
TRI LBM Team: Jose Barreiros et al. A careful examination of large behavior models for multitask dexterous manipulation, 2025.^
Bear Häon, Kaylene Stocking, et al. Mechanistic interpretability for steering vision-language-action models. In Conference on Robot Learning. PMLR, 2025.
Hugo Buurmeijer et al. Observing and controlling features in vision-language-action models, 2026.
Aiden Swann et al. Sparse autoencoders reveal interpretable and steerable features in VLA models, 2026.^
For example, humanoid robot startup Figure lists manufacturing and warehousing among its initial target markets; there are about 14 million US workers currently employed in nonsupervisory (~unskilled) positions in these industries.
Brett Adcock. Roadmap to a positive future powered by AI, 2022.
Bureau of Labor Statistics. The employment situation - March 2026. ^
Chenggang Zhao et al. Insights into DeepSeek-V3: Scaling challenges and reflections on hardware for AI architectures, 2025.^
Linda B. Smith and Michael Gasser. The development of embodied cognition: Six lessons from babies. Artificial Life, 11(1-2):13–29, 2005.^
While our primary focus (and personal expertise) is on technical safety research, it is our understanding that research on physical AI governance is also very neglected:
Jared Perlo et al. Embodied AI: Emerging risks and opportunities for policy action, 2025.^
Bear Häon, Kaylene Stocking, et al. Mechanistic interpretability for steering vision-language-action models. In Conference on Robot Learning. PMLR, 2025.
Hugo Buurmeijer et al. Observing and controlling features in vision-language-action models, 2026.
Aiden Swann et al. Sparse autoencoders reveal interpretable and steerable features in VLA models, 2026.^
Alexander Robey et al. Jailbreaking LLM-controlled robots. In ICRA 2025.^
Kensuke Nakamura et al. Generalizing safety beyond collision avoidance via latent-space reachability analysis. In Robotics Science Systems, 2025.
Ravi Pandya et al. From refusal to recovery: A control-theoretic approach to generative AI guardrails. In Proceedings of IASEAI Conference, 2026.^
Rhitu Chatterjee. Their teenage sons died by suicide. now, they are sounding an alarm about AI chatbots, 2025.^
Troy Griggs and Daisuke Wakabayashi. How a self-driving Uber killed a pedestrian in arizona, 2018
Talia Soglin and Alice Yin. Food delivery robots shatter two Chicago bus shelters. "Two in seven days is not great," alderman says, 2026.^
Bear Häon, Kaylene Stocking, et al. Mechanistic interpretability for steering vision-language-action models. In Conference on Robot Learning. PMLR, 2025.^
Hugo Buurmeijer et al. Observing and controlling features in vision-language-action models, 2026.
Aiden Swann et al. Sparse autoencoders reveal interpretable and steerable features in VLA models, 2026.^
Kensuke Nakamura et al. Generalizing safety beyond collision avoidance via latent-space reachability analysis. In Robotics Science Systems, 2025.^
Pierre Sermanet et al. Generating robot constitutions benchmarks for semantic safety, 2025.
Discuss