If AI Agents Start Running Machines, Where Is the Opening for Small Teams?
A new standard lets agents operate physical devices. Small teams should prepare procedures, not robots.
One of the past two weeks' AI announcements is easy for a small team to scroll past: Anthropic opened a research preview of the Model Hardware Standard (MHS), a shared specification that lets AI agents safely operate physical devices. The first group invited in is scientific research labs and advanced manufacturers. It sounds like news for someone else, but the signal it carries is about the order in which automation leaves the screen.
What does it actually mean for an agent to run a machine?
It does not mean models suddenly got smarter. It means machines and models can finally speak a common language. MHS is a shared driver specification that lets an agent discover instruments such as microscopes, liquid handlers and robotic arms, and operate several of them in parallel.
What blocked physical automation was never intelligence, it was plumbing. Every instrument shipped its own vendor interface, so someone had to hand-write a translator for each pair of devices. MHS is model-agnostic and reachable over MCP, and Anthropic has said it plans to open-source the spec once safety work is further along. The more telling part is who showed up: AWS is adding support through Strands Robots, its library for connecting agents to physical devices, Automata through its LINQ lab automation platform, Tecan for its Fluent liquid handlers, and Universal Robots on its robotics platform, with Danaher also named as a partner. A standard comes alive when equipment makers adopt it, not when it is announced.
One caution for small teams: this is not "anyone can now run a factory with AI." It is a limited research preview. So the correct move today is not adoption but organization. When MCP spread through software tooling, the teams that won early were not the ones that swapped models fastest, but the ones whose workflows and data were already written down.
Where is the real opening for a small team?
The opening is not in building robots. It is in cleaning up the operating rules of businesses that already own equipment. Adapter code gets absorbed by the standard, and what keeps its value afterward is procedure, approval and record-keeping. Those three are the assets a small team can accumulate right now.
- Build an equipment register: model name, control method (vendor SDK, serial, USB, or physical buttons only), whether remote control is possible, firmware version — all on one page.
- Split reversible from irreversible actions: measuring, photographing and status checks can be undone. Heating, cutting, dispensing reagent and shipping cannot. First-wave automation touches only the first group.
- Pick exactly one human sign-off point: a human at every step is not automation, and a human nowhere is an incident. The default place is immediately before the first irreversible action.
- Decide the log format in advance: which command ran, on whose approval, when, and with what result. One photo and one log line is enough.
- Add standard support to your purchasing criteria: simply asking a vendor whether an external control API exists and whether its documentation is public changes the options you have three years from now.
A coffee roastery, a small 3D printing shop, a dental lab or a local testing facility cannot use MHS today. But a shop with roasting profiles and result photos already organized, plus a written line for "machine up to here, human from here," can wire things up in days once the standard opens. A shop with none of that will still be doing discovery work on day one.
What should you do this week?
You do not need a robotics roadmap. The goal for this week is to pick one repeated physical task and make it observable. In order:
- Write down one physical task you repeat at least three times a week — inventory counts, machine warm-up, sample labeling.
- Describe it in ten lines or fewer, in the order a human does it. A procedure that lives only in someone's head cannot be automated.
- Mark the irreversible lines and place an approval step right before them.
- Give the task eyes before hands: have photos, temperatures and quantities recorded automatically.
- After two weeks of records, hand over exactly one reversible action.
Physical equipment is now walking the path software tools already walked with MCP. What a small team should prepare is documentation, not hardware. Teams with procedures and logs will climb aboard the day the standard opens; teams without them will spend a year figuring out what they own.