🔍 Read the full analysis: When AI Acts In Your Name, Who Has To Explain What Happened? on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- 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. Drawing on legal examples and organizational risks, the book argues that financial liability, the duty to explain and fix an agent’s actions, and moral responsibility can fall on different people.
Thorsten Meyer published a new ebook in October 2026 asking who must answer when an AI agent acts on a person’s or company’s behalf. Many Hands: Who Answers When the Agent Acts in Your Name? focuses on a practical problem as agents begin handling purchases, payments and contract terms: the party financially responsible may not be the person who can explain or correct what the system did.
Meyer introduces the issue with a fictional composite business owner named Theresa. In the example, a purchasing agent accepts a supplier’s terms overnight, securing a 7% lower price per tonne but committing the company to buy 120 tonnes of steel over 12 months, with no cancellation right. The commitment is valued at about €370,000. The agent does not know Theresa had agreed the previous day to divide next year’s purchases with another supplier.
The scene is an illustration, not a reported transaction. Meyer writes that the agent followed its rules and recorded its steps, while the purchasing lead says the record contained nothing incorrect but did not reflect what Theresa wanted. The example frames the book’s distinction between who pays, who inside an organization must explain and repair the outcome, and who bears moral responsibility.
Meyer says the ebook’s proposed safeguards include assigning a named person to each agent, limiting its access to what its task requires, preserving records of decisions, and providing a way for affected people to raise concerns. He also argues that people should sign off on an agent’s actions only when they have time, relevant competence, enough information and the authority to refuse. These are the author’s recommendations, not a description of a new law or binding standard.
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
Responsibility Beyond the Final Click
The question matters because an agent can take consequential actions while responsibility is divided among the organization deploying it, the people who set its rules, and the vendor supplying its software. A log may show what the system did without establishing whether anyone had the authority, information or realistic chance to stop it. That makes explanation and remedy an operational issue, not just a question for courts after a loss.
Meyer argues that the closest human to an automated decision can end up carrying blame even when that person did not design the system or control its broader conditions. Conversely, a company may have a contractual route to shift some financial risk while people affected by the decision still lack a clear contact or way to challenge it. The book’s three-part framework separates legal liability, organizational accountability and moral responsibility so they are not treated as interchangeable.
For businesses adopting agents, the argument points to concrete governance questions: which actions can an agent take without approval, who reviews exceptions, and who is responsible for explaining a decision to a supplier, customer or employee? The ebook raises those questions but does not establish how any particular dispute would be resolved.
Products Worth Considering
Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
Samsung 27-inch Odyssey OLED G6 QD-OLED QHD Gaming Monitor
LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1
As an affiliate, we earn on qualifying purchases.
From Many Hands to Agent Systems
The book’s title draws on political philosopher Dennis F. Thompson’s 1980 discussion of the “problem of many hands”: when numerous people contribute to an outcome, it can be hard to identify who is responsible. Meyer argues that AI agents add more participants and distance, while acting at speed on behalf of users or organizations. The phrase is a framework for the book, not a legal finding.
Meyer connects the argument to earlier cases. He discusses the 2018 fatal crash involving a self-driving test vehicle in Tempe, Arizona, and the Dutch childcare benefits scandal, in which families were wrongly required to repay benefits. In the Tempe case, the US National Transportation Safety Board identified multiple failures and contributors; the criminal case reached the vehicle operator, who pleaded guilty to endangerment. Meyer uses the case to examine how blame can settle on the nearest human while system design and oversight also warrant scrutiny.
The source also points to European product liability rules, describing their coverage of software-related injury and damage to private property or data while saying pure financial losses, such as a bad contract or incorrect payment, are outside that framework. This is Meyer’s summary; the precise legal position depends on the applicable law and facts. He further says model-provider contracts may limit liability to about a year of fees, leaving customers with losses they cannot pass on. Readers should treat those statements as the author’s account, not legal advice.
“protects the integrity of the technological system, at the expense of the nearest human operator.”
— Madeleine Clare Elish, as quoted in Meyer’s book
Legal Exposure Depends on the Case
The ebook’s scenarios and policy arguments do not determine who would be liable in a real agent-related dispute. That would depend on the relevant jurisdiction, the agreements in place, the actions taken and the harm suffered. The source material does not provide a court ruling on the fictional steel purchase or a settled legal test for assigning responsibility when an AI agent accepts business terms.
Details behind Meyer’s broad claims about product liability and vendor contract limits are not set out in the supplied material, including which laws or contract terms apply in each situation. The source describes the steel scenario as a composite, and it does not report that a real company incurred the stated commitment. It also offers no data measuring how often agents make comparable decisions or how much financial loss they cause.
Governance Questions for Deployers
The ebook is available as a first-edition ebook, published in October 2026, through retailers listed by Meyer, including Apple Books, Barnes & Noble, Kobo and Thalia. The source also promotes a short video about the book, narrated using an AI voice clone of Meyer.
No court decision, regulatory action or new compliance deadline is announced in the material. For organizations using agents, the immediate questions raised are practical: identify an accountable owner for each system, set limits on what it can do, keep usable decision records and give affected people a route to seek review. Whether those steps become formal requirements will depend on future law, regulation and case outcomes.
Key Questions
What is Many Hands about?
Thorsten Meyer’s ebook examines who pays, who explains and fixes an outcome, and who bears moral responsibility when an AI agent acts for a person or organization.
Is the €370,000 steel purchase a real incident?
No. Meyer describes Theresa and the purchase as a composite scenario used to introduce the book’s argument. The supplied material does not report an actual company or transaction behind it.
Does the book say AI agents are legally liable?
The book asks how responsibility should be assigned; it does not establish that an AI agent itself is legally liable. Legal responsibility depends on the applicable law and facts, including the conduct of people and organizations involved.
What safeguards does Meyer recommend?
He proposes naming a responsible person for each agent, limiting its permissions, recording who made decisions and giving affected people a way to raise concerns. He also argues that human approval is meaningful only when the reviewer has time, competence, information and authority to refuse.
Source: ThorstenMeyerAI.com
