🔍 Read the full analysis: Many Hands: The People Behind An AI Agent’s Actions on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Thorsten Meyer published Many Hands: Who Answers When the Agent Acts in Your Name? as an ebook in October 2026. The book examines how legal liability, organizational responsibility and moral accountability can diverge when AI agents make purchases, accept terms or otherwise act for people and businesses. Its examples and conclusions are presented in the book and source material; the material does not establish new legal rulings or a specific policy change.
Thorsten Meyer published Many Hands: Who Answers When the Agent Acts in Your Name? as an ebook in October 2026, arguing that accountability can split among the people and organizations involved when an AI agent acts on someone’s behalf. The book focuses on a practical question for businesses adopting agents that can buy, pay or accept terms: who bears the loss, who must explain and repair the outcome, and who should be held morally responsible?
Meyer introduces the question with a fictional composite scenario, not a reported incident. In it, a purchasing agent accepts a steel supplier’s terms at 2:14 a.m., securing a seven-percent lower price in return for a 120-tonne, 12-month commitment with no cancellation right. The commitment is valued at about €370,000. The owner, Theresa, had previously agreed to split the next year’s volume with another supplier, but that information was not available to the agent.
The source says the agent followed its rules and recorded its actions. A purchasing lead in the scenario says, “Nothing in it was wrong, and nothing in it was what she wanted.” The example is used to distinguish compliance with an agent’s instructions from whether the outcome reflects a person’s intentions. It should not be read as evidence of an actual supplier contract or a documented company dispute.
Meyer divides accountability into three questions: who pays, a matter of law and contracts; who must explain and fix the result inside an organization; and who should have acted differently, a moral question. He says the book is available as an ebook through retailers including Apple Books, Barnes & Noble, Kobo and Thalia. The source describes it as the first edition, published in October 2026.
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
The issue matters because software agents are being designed to do more than produce answers: they can make purchases, accept terms, send payments and change data in another party’s name. If the instructions are incomplete or the agent lacks important information, an action can be technically permitted yet still create a costly result. The question is not only whether the system functioned as specified, but also who had the authority and opportunity to prevent the harm.
Meyer’s framework highlights that responsibility may not fall on the same party in every sense. A contract could assign financial loss one way, an organization could expect an employee to investigate and repair the problem, and observers could judge that designers or senior decision-makers should have acted differently. Those answers can diverge, particularly when decision-making is spread across developers, vendors, managers and operators.
The book proposes practical measures such as naming a person responsible for each agent, limiting access to what its task requires, keeping records of decisions and providing a route for affected people to raise concerns. These are Meyer’s recommendations, not reported regulatory requirements. Their relevance is that they address routine questions—who authorized an action and who can stop it—before a dispute occurs.
Products Worth Considering
Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
Brother TD-2020A 2‑Inch Direct Thermal Desktop Label Printer with USB
Samsung 27 Odyssey OLED G5 (G50SF) QHD QD-OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
The Examples Behind Meyer’s Argument
Meyer connects the accountability problem to 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 identify who is responsible. Meyer argues that AI agents add another participant and can increase the distance and speed between a decision and the people affected by it. That is the book’s framing, rather than a claim that agents created the underlying problem.
One example discussed in the source is the 2018 fatal crash involving an Uber self-driving test vehicle in Tempe, Arizona. The source attributes findings to the U.S. National Transportation Safety Board: the system detected pedestrian Elaine Herzberg 5.6 seconds before impact, did not settle on what she was, and had been designed to delay emergency braking for one second. The source says the board identified failures and roles involving the operator, company risk assessment and oversight, safety culture, the state and the pedestrian. The operator pleaded guilty to endangerment. Meyer uses the case to ask how responsibility is assigned when a human is expected to supervise a system under difficult conditions.
The book also discusses the Dutch childcare benefits scandal, in which tens of thousands of families were wrongly required to repay benefits. According to the supplied material, the Dutch cabinet resigned in January 2021, and a government report in September 2026 recognized more than 44,000 affected people. Meyer presents it as an example of responsibility dispersed across institutions and decision-makers, not as an AI-agent case. The examples provide context for his argument that accountability challenges existed before autonomous agents became capable of taking direct actions.
Legal Duties and Liability Remain Open
The source presents Meyer’s interpretation of law and policy, but does not provide a full legal analysis or establish how a court would resolve a particular AI-agent dispute. It says Europe’s product liability rules cover software-related injury, damage to private property and harm to private data, but do not cover pure financial loss such as a bad contract or mistaken payment. The scope and application of those rules depend on the relevant law and facts; readers should not treat this account as legal advice.
The material also says vendor contracts may cap a model provider’s liability at roughly a year of fees, but it does not identify specific contract terms or show how broadly that figure applies. The fictional steel purchase does not establish who would legally owe money in a real case. No new court decision, regulation or enforcement action is announced in the source. It remains unclear how responsibility would be divided in future disputes involving agents, their users, developers and suppliers.
The Accountability Debate Moves On
The immediate development is the release of Meyer’s ebook; the supplied material gives no date for a launch event, new edition or follow-up publication. Readers can consult the book through the retailers named by its publisher. Meyer’s accompanying video is described as a five-minute overview with animated charts and narration using an AI voice clone of the author.
For organizations using agents, the questions raised by the book are practical: who is named as responsible for each system, what actions can it take, what records are kept, and how can a person affected by a decision seek review? Whether these practices become contractual standards, regulatory requirements or internal policies is not established by the source. Further clarity would depend on specific contracts, applicable laws and future legal or regulatory decisions.
Key Questions
What is Many Hands about?
Thorsten Meyer’s ebook examines who should pay, explain and take moral responsibility when an AI agent acts in a person’s or organization’s name.
Is the steel purchasing story a real incident?
No. The source identifies Theresa and the purchasing scenario as a fictional composite built from common situations. It is an illustration, not a reported €370,000 contract.
Does the book announce a change in law?
No new law or court ruling is announced in the supplied material. Meyer discusses existing legal frameworks and argues that some agent-related losses may not fit neatly within product liability rules.
What steps does Meyer suggest for organizations?
The source says Meyer recommends assigning a named person to each agent, limiting its permissions to the task, recording who made decisions and giving affected people a way to raise concerns.
Source: ThorstenMeyerAI.com
