🔍 Read the full analysis: AI Agents In Our Name: Who Answers For What They Do? 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 argues that responsibility for agent actions splits between legal liability, organizational response and moral accountability, and that existing rules may not cover common financial losses from agent mistakes.
Writer and AI systems developer Thorsten Meyer announced the October 2026 ebook release of Many Hands: Who Answers When the Agent Acts in Your Name?, a book examining who is responsible when AI agents buy, pay, accept terms or otherwise act for people and organizations. Meyer frames the issue as three separate questions: who pays for a loss, who must explain and fix it, and who should be held morally accountable.
The book opens with a purchasing scenario Meyer describes as a composite, not a documented real incident. A business agent accepts a steel supplier’s terms, securing a seven-percent price reduction in exchange for a commitment to buy 120 tonnes over a year, worth about €370,000. The owner had agreed the previous day to divide the next year’s volume with another supplier, but the agent was not told. Meyer says the agent followed its rules and recorded its actions, even though the result was contrary to the owner’s intention.
Meyer’s central argument is that the question “Who is liable?” can obscure different kinds of responsibility. Legal responsibility concerns who pays under law and contract; organizational responsibility concerns who has to investigate, explain and repair a problem; and moral responsibility concerns who should have acted differently. The book argues that these answers can point to different people.
The author also identifies safeguards for delegating authority to an agent: a named human owner, permissions limited to the task, records showing who or what made decisions, and a way for people affected to raise concerns. Meyer says records should support learning, rather than simply become tools for punishing staff. The ebook is listed as available through Apple Books, Barnes & Noble, Kobo and other retailers.
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
Separating Liability From Oversight
The issue matters as agents move beyond generating recommendations and begin taking actions with financial and operational consequences. A system can carry out an authorized task according to its instructions while still producing an outcome its operator did not intend. In that situation, tracing the action in a log may help explain what happened, but it does not by itself settle who bears the cost or must put matters right.
Meyer argues that existing legal protections may leave some of these losses unresolved. He says the European Union’s product-liability rules cover software and certain harms, including injury, damage to private property and damage to private data, but do not cover pure financial loss, such as an incorrect payment or an unfavorable contract. That is the author’s description of the rules; the source material does not provide a legal opinion or analysis of how particular courts would apply them to an agent incident.
The book also points to an imbalance in vendor contracts. Meyer says model-provider terms quoted in the book cap liability at roughly one year of fees, potentially leaving customers unable to pass on losses. The practical question for companies is not only whether they can deploy an agent, but whether they have assigned authority, review and recovery responsibilities before it acts.
Products Worth Considering
LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1
Samsung 27-inch Odyssey OLED G6 QD-OLED QHD Gaming Monitor
Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Many Hands to Agent Actions
The title draws on political philosopher Dennis F. Thompson’s “problem of many hands,” a term Meyer says was introduced in 1980 to describe how responsibility becomes difficult to assign when many people contribute to an outcome. Meyer’s argument is that agents add distance and speed to an existing problem: an action may involve model developers, software providers, managers, operators and the organization that delegates authority.
To illustrate how accountability can land on the person closest to an event, Meyer discusses the 2018 self-driving test-car fatality in Tempe, Arizona. He cites the U.S. National Transportation Safety Board’s findings that the system detected Elaine Herzberg before the collision but did not settle on what she was and, by design, withheld emergency braking for one second. The book says the board identified multiple contributors and that the safety operator pleaded guilty to endangerment. Meyer connects the case to anthropologist Madeleine Clare Elish’s phrase “moral crumple zone” for a human operator who absorbs blame while a larger system remains less visible.
Meyer also refers to the Dutch childcare benefits scandal, in which families were wrongly required to repay benefits. The source material says the Dutch government reported in September 2026 that more than 44,000 people had been recognized as affected. These examples are presented as context for how institutional processes can diffuse responsibility; they are not cases involving the purchasing-agent scenario, which Meyer explicitly labels a composite.
““[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
Where Legal Responsibility Falls
The source material does not identify a real company, supplier or transaction behind the opening steel-purchase example; Meyer says Theresa and the scenario are composite. It therefore should not be read as evidence that a specific business lost €370,000 or that an agent actually accepted those terms.
Nor does the material establish how a court would decide liability in a comparable real-world dispute. The result would depend on facts such as the agent’s permissions, the organization’s instructions, the contract terms and the laws that apply. Meyer’s account of European product-liability coverage and vendor caps is the author’s summary; the source does not include the relevant contract wording or a detailed legal analysis.
It is also unclear how widespread the contract provisions Meyer describes are, or how the book’s proposed safeguards would perform across different agent systems and industries. The announcement presents an argument and practical recommendations, not evidence from a reported trial or a measured evaluation of deployed agents.
The Book’s Accountability Test
The ebook is available through the retailers listed by Meyer, and the author has also published a short video introducing the book. The next practical test for its argument will come as organizations use agents to make purchases, accept terms and alter business data: who is named as responsible, what authority is granted, and how can an affected person seek review?
The source material does not announce a specific legal decision, regulatory deadline or company policy change tied to the release. For now, the development is the publication of Meyer’s book and its call to distinguish who pays, who repairs the harm and who should answer for the decision.
Key Questions
What is Many Hands about?
Thorsten Meyer’s October 2026 ebook examines accountability when AI agents act on behalf of people or organizations. It separates legal liability, organizational duties to investigate and repair, and moral responsibility.
Did the steel-purchasing incident really happen?
The source describes it as a composite scenario used to open the book. It does not identify it as a real transaction or a documented company loss.
Who is legally responsible when an AI agent makes a bad deal?
The announcement does not give a universal legal answer. Responsibility in a real dispute would depend on the relevant law, contract, instructions and agent permissions; Meyer’s book argues that legal liability can differ from organizational and moral responsibility.
What safeguards does Meyer recommend?
He proposes assigning a named person to each agent, limiting the agent’s permissions to its task, keeping records of decisions and giving affected people a way to raise concerns. He says records should be used to learn from problems rather than only to punish.
Source: ThorstenMeyerAI.com
