🔍 Read the full analysis: Many Hands: Who Answers When An AI Agent Acts In Your Name? on ThorstenMeyerAI.com
Get movie nights delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Thorsten Meyer published Many Hands: Who Answers When an Agent Acts in Your Name? as an ebook in October 2026. The book examines how legal liability, organizational responsibility and moral accountability can fall on different people when AI agents make decisions or commitments.
Thorsten Meyer published Many Hands: Who Answers When an Agent Acts in Your Name? as an ebook in October 2026, framing a growing governance question as AI agents move beyond answering prompts to buying, paying, accepting terms and changing data. The book argues that responsibility can split among the person or company that pays for a mistake, the people expected to explain and repair it, and those who should have acted differently.
Meyer opens with a purchasing scenario involving Theresa, a business owner. An agent accepts a steel supplier’s terms, securing a 7% lower price per tonne while committing the company to buy 120 tonnes over 12 months, without a cancellation right. The commitment is valued at about €370,000. The day before, Theresa had agreed to divide the following year’s volume with another supplier, but the agent was not given that information. Meyer identifies Theresa as a composite character, not a report of a specific transaction.
In the scenario, the agent followed its rules and recorded its actions, yet the result conflicted with the owner’s intentions. Meyer uses that tension to distinguish legal liability—who pays—from organizational responsibility—who explains and fixes the outcome—and moral responsibility—who should have acted differently. The book’s central point is that these questions can have different answers.
The ebook’s listed first edition is dated October 2026. Meyer says his discussion draws on examples including the 2018 fatal crash involving an Uber self-driving test vehicle in Tempe, Arizona, and the Dutch childcare benefits scandal. The supplied material also describes the book’s proposed accountability measures: a named person for each agent, permissions limited to the task, records showing who made which decision, and a route for affected people to seek help.
Many Hands · the core idea
One question, three answers
"Am I liable if the agent does it in my name?" sounds like one question. The book splits it into three, because agent systems pull the answers apart.
Decided by courts, contracts and insurers, on their own timetable.
In Theresa's caseHer company will almost certainly pay for the steel, whatever it later recovers from others.
Decided inside the organization: who must say what happened and what will change.
In Theresa's caseTheresa explains it to the second supplier, her staff and perhaps her bank.
Who owes the people affected an acknowledgment. Often answered last, if at all.
In Theresa's caseStill open when she reaches the motorway.
The hands behind one overnight order
Introduction · a composite scene from the book. None of them saw the acceptance before it went out.
- Model makertrained the language model
- Vendorbuilt the agent on top of it
- Consultantwrote its rules with her staff
- Supplier's portalaccepted the declaration at 2:14 a.m.
- Her companyswitched it on; Theresa signed the rules
“The moral crumple zone protects the integrity of the technological system, at the expense of the nearest human operator.”Madeleine Clare Elish (2019), quoted in Chapter 1
Source: Thorsten Meyer, Many Hands: Who Answers When the Agent Acts in Your Name? (ebook, October 2026; law as of 16 October 2026), Introduction and Chapter 1. Theresa is a composite built from common situations, labeled as such in the book.
Powered by Thorsten Meyer AI
Accountability Beyond the Agent
The issue matters because an agent can take actions with financial and operational consequences while responsibility is distributed across users, managers, vendors and system designers. A well-kept log may show what the software did without settling who had authority to approve the action, who had enough information to prevent it, or who must put things right.
Meyer argues that people closest to an incident can become the visible focus of blame, even when decisions about system design, oversight and working conditions shaped what happened. That concern resembles what anthropologist Madeleine Clare Elish calls the “moral crumple zone”: a human operator may absorb blame for a system’s failures. The book presents this as an accountability problem, not proof that any particular agent deployment has already caused a specific loss.
For organizations adopting agents, the practical stakes include contract review, delegated authority, audit trails and a clear process for challenging actions. Meyer’s framework asks readers to avoid treating “the human” as a single answer: the person who signed off may not be the person who can explain the decision or prevent a repeat.
Popular right now
Bose QuietComfort Wireless Noise-Cancelling Over-Ear Headphones, Black
Dyson Ball Animal 3 Extra Upright Vacuum
Ninja Flip Toaster Oven and Air Fryer, 8-in-1, Stainless Steel, SP151
As an affiliate, we earn on qualifying purchases.
The book takes its title from political philosopher Dennis F. Thompson’s 1980 description of the “problem of many hands”: when many people contribute to an outcome, it can be difficult to assign responsibility. Meyer argues that AI agents add distance and speed to this familiar problem, while allowing software to act in someone else’s name.
One example Meyer discusses is the 2018 Tempe crash in which a self-driving test vehicle struck and killed pedestrian Elaine Herzberg. According to the U.S. National Transportation Safety Board findings cited in the source material, the system detected Herzberg 5.6 seconds before impact, did not settle on what she was, and had emergency braking delayed by design. The investigation identified issues involving the vehicle operator, company risk assessment and oversight, safety culture, the state and the pedestrian. The example illustrates how a legal outcome focused on an individual can coexist with wider questions about system design.
Meyer also points to the Dutch childcare benefits scandal, in which tens of thousands of families were wrongly required to repay benefits. The source says the Dutch cabinet resigned in January 2021 and quotes the prime minister describing responsibility as joint when the whole system failed. These cases predate today’s broader use of AI agents; Meyer uses them to show that distributed accountability is not a problem created by agents alone.
“protects the integrity of the technological system, at the expense of the nearest human operator.”
— Madeleine Clare Elish, as quoted in Meyer’s book
Where Liability Still Falls
The source material presents the book’s interpretation of law and policy; it does not provide a court ruling about the hypothetical steel purchase or establish how a particular company would be held liable for an agent’s actions. Meyer says Europe’s product liability rules cover software-related injury, private property and private data, but not pure financial loss, such as a bad contract or incorrect payment. That legal account is attributable to the author and is not a substitute for advice about a specific dispute.
The source also says some model-provider contracts cap liability at about a year of fees, but it does not identify the contracts or providers behind that generalization. The precise terms, governing law and facts of any agent-related dispute would matter. It is also unclear from the material how widely organizations currently use the proposed controls or whether they measurably reduce losses.
Questions for Agent Deployments
The immediate development is the ebook’s October 2026 release. Meyer lists it for sale through several digital book retailers and provides a short accompanying video about the book. The source does not announce a policy decision, court case or regulatory milestone tied to its publication.
For readers responsible for deploying agents, the next steps raised by the book are practical: specify what an agent may commit to, assign a named human owner, retain records of approvals and actions, and provide a way for affected people to contest outcomes. Whether those measures are sufficient will depend on the system, the organization’s authority structure and the applicable law. The broader question remains how responsibility should be divided when an agent acts quickly, but the people who designed, authorized and oversee it are several steps removed.
Key Questions
What is Many Hands about?
Thorsten Meyer’s ebook examines who pays, who fixes a problem and who bears moral responsibility when an AI agent acts on someone’s behalf. It uses examples from procurement, autonomous driving and government administration.
Is the steel purchase in the opening a real incident?
No. Meyer describes Theresa and the supplier commitment as a composite scenario built from common situations. The source does not report a real company losing €370,000 in this transaction.
Does the book say an AI agent is legally liable?
The book separates the agent’s action from the legal question of who pays. The source does not establish a general rule that an AI agent itself is liable; responsibility would depend on law, contracts and the facts of a case.
What accountability measures does Meyer propose?
He proposes assigning a named person to each agent, limiting permissions to the task, keeping records of decisions and providing a way for affected people to seek review or help.
Source: ThorstenMeyerAI.com
