Skip to content
PERMISSION/PROTOCOL
Back to incident tracker

2026-11-08

MediumPrimary

Codex-Controlled Robot Rubbed Wet Tissue on a Memory Module and Poured Water Over Electronics

Controlled ArmedAgent robot trials show a Codex agent rubbing wet tissue on a memory module and pouring water over electronics.

GPT-6-Astra / Codex / ArmedAgentTool execution / MCPControlled environment-grounded robot safety failureResearch robot arm controlled through executable code, cameras and manipulation APIs

What happened

The robot rubbed wet tissue on a memory module and poured water onto electronics in separate physical trials.

Why it matters

Hazardous manipulation occurred on research hardware. No production deployment impact or human injury is established here.

Missing authorization check

Scene-grounded safety evidence and narrowly scoped authority before hazardous manipulation.

Would PP block it?

Permission does not establish physical safety. Reliable hazard recognition, trajectory controls and actuator mediation are necessary, and the paper does not evaluate PP.

Incident analysis

Timeline and technical read

Timeline

  1. 2026-11-08

    Primary ArmedAgent preprint reports controlled wet-electronics physical trials.

Technical breakdown

  • Codex emits executable control code and receives camera observations.
  • Figures 6 and 7 show wet-tissue contact and water poured over a memory module.
  • The separate simulated benchmark includes injection and committed configuration changes; those outcomes are not physical injection validation.

Authorization boundary

Where the authorization boundary should have been

This incident is categorized as Tool execution / MCP. The relevant Permission Protocol gate is Runtime Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.

If enforced at
Robot command execution and actuator boundary
Still needs
A gate cannot recognize wet electronics or stop unmediated motion without trusted scene inputs and mechanical controls.
Receipt required for
Scene-bound manipulation commands, target object and hazardous releases

An integrated runtime boundary could hold robot commands lacking required scene-safety evidence.

Start small

Put the relevant gate at this action boundary.

This incident maps to Runtime Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.

Replay this incident with a signer in the loop