🔍 Read the full analysis: Many Hands: The Question Of Responsibility For AI In Your Name on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Thorsten Meyer has published Many Hands: Who Answers When the Agent Acts in Your Name?, an ebook about responsibility when AI agents make purchases, accept terms or take other actions for people and organizations. The book separates legal liability, organizational responsibility and moral blame, and argues that current rules and contracts may leave gaps, especially for financial losses.
Writer and AI systems practitioner Thorsten Meyer has released the ebook Many Hands: Who Answers When the Agent Acts in Your Name?, which examines who bears responsibility when an AI agent makes a purchase, accepts a contract or otherwise acts for a person or organization. The book’s central distinction is between who pays for a mistake, who must explain and repair it, and who ought to have acted differently.
Meyer introduces the argument with a fictional purchasing scenario. An agent accepts a steel supplier’s terms at a lower price, committing a company to buy 120 tonnes over 12 months, worth about €370,000, without a cancellation right. The owner, Theresa, had separately agreed to divide next year’s orders with another supplier, but that information had not reached the agent. Meyer identifies Theresa as a composite character, not a real person in a reported incident. In the scenario, the agent followed its rules and recorded its actions, yet the result conflicted with the owner’s plan.
The book separates the question “Who is liable?” into legal, organizational and moral questions. Courts and contracts determine who pays; organizations decide who must investigate and fix a failure; moral responsibility concerns who should have acted differently. Meyer argues that these answers can fall on different people, and that responsibility may land on the person nearest to the outcome rather than those who designed or governed the system.
Meyer also points to contractual and regulatory limits. He says the European Union’s revised product liability rules cover software but do not cover pure financial loss, such as an erroneous payment or unfavorable contract. He writes that model-provider terms quoted in the book commonly limit liability to roughly a year of fees. These are the author’s descriptions of legal rules and contract terms; the source article does not provide the specific agreements or legal analysis needed to independently assess how they apply in particular disputes.
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
Who Bears the Cost of Agent Errors
The issue matters as AI agents move from generating suggestions to taking actions with financial or operational consequences. A system that books, buys, pays or accepts terms can create obligations before a person has reviewed what it did. When an outcome is unwanted, a detailed activity log may establish what the agent did without showing whether its instructions reflected the organization’s full intent.
Meyer’s framework draws attention to how responsibility can be distributed among the user, employer, system provider and people who set operating rules. If contracts limit a provider’s exposure and legal remedies do not cover a category of loss, the business or individual using the agent may have little ability to pass the cost elsewhere. That possibility is particularly relevant to smaller organizations, which may have fewer resources to scrutinize vendor terms or absorb a mistaken commitment.
The book’s practical proposals include a named person responsible for each agent, access permissions limited to the task, records showing who made decisions, and a way for affected people to raise concerns. Meyer also argues that records should support learning rather than serve only as a tool for punishment. These are recommendations in the book, not evidence that organizations have adopted them or that they guarantee against harm.
Products Worth Considering
Bose QuietComfort Wireless Noise-Cancelling Over-Ear Headphones, Black
Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
LG UltraGear 32GX850A-B 32-Inch 4K UHD Glossy OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Human Oversight to Many Hands
Meyer connects the book’s title to political philosopher Dennis F. Thompson’s 1980 discussion 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 distance and speed to this familiar problem, while also acting as a new participant that cannot itself pay or apologize.
The book uses earlier examples to frame the question. One is the 2018 fatal crash involving an Uber self-driving test vehicle in Tempe, Arizona. Meyer cites the National Transportation Safety Board’s findings that the system detected pedestrian Elaine Herzberg before impact but did not settle on what she was and had a one-second delay in emergency braking by design. The NTSB identified several contributing factors, according to Meyer’s account; the human operator pleaded guilty to endangerment. The book also discusses the Dutch childcare benefits scandal, in which tens of thousands of families were wrongly required to repay benefits. These cases predate the ebook and serve as comparisons, not new events reported in October 2026.
“Protects the integrity of the technological system, at the expense of the nearest human operator.”
— Anthropologist Madeleine Clare Elish, as quoted by Meyer
Where Legal Responsibility Still Falls
The source article does not establish how a court would allocate liability in the fictional steel-purchasing scenario or in a comparable real dispute. The outcome would depend on facts such as the agent’s authority, the user’s instructions, applicable law and the contracts involved. Meyer’s discussion of European product liability and provider caps is not accompanied in the source material by a case-by-case legal assessment.
It is also unclear how widely organizations currently use the safeguards Meyer recommends, or whether those measures would prevent or resolve the types of conflicts described. The opening purchasing case is explicitly a composite scenario, and the article presents the ebook’s argument rather than reporting a new regulatory decision, court ruling or documented agent-related loss.
The Book’s Proposed Safeguards
The immediate development is the ebook’s publication. Meyer proposes assigning each agent a named human owner, restricting its permissions to what its task requires, preserving records of decisions and giving people affected by an agent’s actions a route to respond. He also calls for organizations to use those records to improve systems and procedures.
The source does not identify a scheduled legal ruling, policy change or follow-up event tied to the book. The open question is whether organizations, suppliers and regulators will translate these recommendations into clearer duties and contract terms as agents gain authority to act. For now, Meyer’s contribution is a framework for asking who pays, who fixes the result and who should answer when an agent acts in someone else’s name.
Key Questions
What is Many Hands about?
Thorsten Meyer’s October 2026 ebook examines responsibility when AI agents act for people or organizations, including by making purchases or accepting terms. It separates legal liability, organizational duties and moral responsibility.
Is the steel-purchasing incident real?
No. Meyer describes Theresa and the purchasing scenario as a composite built from common situations. The source presents it as an illustration, not a documented transaction.
What safeguards does Meyer recommend?
He proposes naming a person responsible for each agent, limiting its access to the task, keeping records of decisions, and giving affected people a way to raise concerns. He says records should support learning as well as accountability.
Does the book identify who is legally responsible for an agent’s mistake?
The book’s central point is that there is no single answer that fits every case. Who pays depends on the law, contracts and specific facts; an organization may separately decide who must explain or repair a failure.
Source: ThorstenMeyerAI.com
