🔍 Read the full analysis: When An AI Agent Acts In Your Name, Who Takes Responsibility? 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 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 fall on different people when AI agents make decisions or commitments on someone’s behalf.
Writer Thorsten Meyer announced the release of Many Hands: Who Answers When the Agent Acts in Your Name?, an ebook about who is responsible when an AI agent makes a decision or commitment on someone else’s behalf. The book argues that who pays, who must explain and repair the outcome, and who bears moral responsibility may be different people—an issue gaining relevance as agents are used to buy, book, pay and change data.
Meyer introduces the book through a fictional composite scenario: a purchasing agent accepts a steel supplier’s terms overnight, securing a lower price but committing a company to buy 120 tonnes over 12 months for about €370,000, with no right to cancel. The owner had separately agreed to divide the following year’s volume with another supplier, but that information had not reached the agent. Meyer says the scenario is illustrative, not a reported real-world incident.
The book separates accountability into three questions: who pays under law and contract, who explains and fixes the outcome inside an organization, and who should have acted differently as a matter of ethics. Meyer’s central point is that these answers can diverge. A system may follow its configured rules while still producing an outcome its operator did not intend.
As practical safeguards, Meyer proposes assigning a named person to each agent, limiting its permissions to the task, recording who made decisions, providing a way for affected people to raise concerns, and using records to improve systems rather than only to punish individuals. These are recommendations presented in the book, not requirements established by the announcement.
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
When Agent Actions Create Business Risks
For organizations using agents to make purchases, accept terms or alter records, the issue is not simply whether software made an error. A decision can be authorized by the system yet conflict with information held elsewhere or with a person’s intentions. That can leave a company facing financial loss, a binding contract or harm to an affected person, while responsibility is spread across users, managers, developers and vendors.
Meyer’s distinction matters because fixing a problem is not the same as paying for it or accepting moral blame. A contract may allocate financial risk one way, while an organization still needs someone to explain what happened and correct it. The book’s proposals focus on making those roles and limits visible before an agent acts.
Products Worth Considering
Samsung 32-Inch Odyssey OLED G8 (G80SH) 4K Gaming Monitor
LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1
Samsung 27 Odyssey OLED G5 (G50SF) QHD QD-OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Human Oversight to Many Hands
The book draws on the idea known as the “problem of many hands,” associated with political philosopher Dennis F. Thompson: when many people contribute to an outcome, it can be difficult to identify who is accountable. Meyer argues that agents add distance and speed to that familiar problem, while acting in a person’s or organization’s name.
To illustrate how responsibility can concentrate on the person nearest an incident, Meyer discusses the 2018 fatal crash involving an Uber self-driving test vehicle in Tempe, Arizona. He cites the National Transportation Safety Board’s account that the vehicle detected pedestrian Elaine Herzberg before impact but did not correctly resolve what it had detected; the board also examined the operator and wider organizational and safety factors. The book connects that case to anthropologist Madeleine Clare Elish’s term “moral crumple zone,” describing how a nearby human operator can absorb blame for a system’s failures.
Meyer also refers to the Dutch childcare benefits scandal, in which families were wrongly required to repay benefits, as an example of responsibility becoming dispersed across institutions. These examples provide context for the book’s argument; they do not establish how liability would be decided in a future case involving an AI agent.
““[The moral crumple zone] protects the integrity of the technological system, at the expense of the nearest human operator.””
— Madeleine Clare Elish, as quoted in Meyer’s book
Liability Depends on the Specific Case
The announcement does not identify a particular dispute, court ruling or new regulation triggered by the book’s release. Its opening steel-purchase example is explicitly a composite scenario, not evidence that a named company incurred the stated commitment.
The material also does not establish how a court would allocate responsibility for a specific agent’s act. That could depend on the agent’s permissions, the information available to it, the user’s instructions, organizational controls and applicable contracts and law. Meyer argues that European product-liability rules do not cover pure financial loss such as a mistaken payment or contract; this is the author’s account, and the announcement does not provide a legal analysis of how those rules would apply in a particular case.
The Debate Moves to Deployment
The ebook is described as available through several retailers, including Apple Books, Barnes & Noble, Kobo and Thalia. The announcement does not give a schedule for policy changes, a legal proceeding or another milestone tied to its release.
For companies deploying agents, the immediate practical questions are whether each system has a clearly responsible owner, whether its authority is limited to its assigned task, and whether its decisions can be reviewed and challenged. How organizations and courts answer those questions will depend on future deployments and specific disputes; the book sets out Meyer’s framework rather than resolving those cases.
Key Questions
What is Many Hands about?
Thorsten Meyer’s ebook examines responsibility when AI agents act for people or organizations. It distinguishes legal liability, organizational responsibility and moral accountability.
Is the steel-purchasing story a real incident?
No. Meyer identifies Theresa and the purchasing scenario as a composite example built from common situations, not a documented case involving a named company.
Does the ebook establish who is legally liable when an agent makes a mistake?
No. It frames the question and discusses relevant risks, but the announcement does not report a new court decision or determine liability for a specific agent action. The answer would depend on the facts, contracts and applicable law.
What safeguards does Meyer propose?
He recommends a named person responsible for each agent, permissions limited to the task, records showing who decided what, a way for affected people to raise concerns, and reviews aimed at learning from incidents.
Source: ThorstenMeyerAI.com
