🔍 Read the full analysis: AI Agents, Human Responsibility, And The Question Of Who Answers 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’s ebook Many Hands, published in October 2026, examines who is responsible when AI agents make purchases, accept terms or otherwise act for people and organizations. It separates legal liability, organizational duties to explain and repair harm, and moral responsibility, while arguing that the rules for allocating losses remain unsettled.
Thorsten Meyer published Many Hands: Who Answers When the Agent Acts in Your Name? as an ebook in October 2026, addressing how responsibility is divided when AI agents make decisions and commitments on behalf of people or businesses. The book separates the question of who pays for a loss from who must explain or fix it, and who should be held morally responsible.
Meyer introduces the argument with a composite purchasing scenario: an agent accepts a supplier’s terms, securing a lower price but committing a company to a 12-month purchase worth about €370,000. The owner had separately agreed to divide future volume with another supplier, but the agent had not been told. The scenario is illustrative, not a reported case. Meyer writes that the agent followed its rules and recorded its actions, while the purchasing lead says the record did not reflect what the owner wanted.
The book’s central framework divides accountability into three questions: who pays, a matter for law and contracts; who explains and repairs the outcome, an organizational responsibility; and who should have acted differently, a moral judgment. Meyer argues that these answers can point to different people, particularly when a system’s designers, deployers, operators and users all contribute to an outcome.
Meyer also argues that contract terms and product-liability rules may leave financial losses difficult to recover. He says the European product-liability framework covers software but does not cover pure financial loss, such as a bad contract or incorrect payment. He further says model-provider contracts cited in the book commonly limit liability to roughly a year of fees. These are the author’s descriptions and arguments; the supplied material does not include the underlying legal texts or contract examples for independent verification.
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 an Agent’s Mistakes?
The issue matters as agents move from producing recommendations to booking, buying, paying, accepting terms and changing data. An error can create a binding commitment or a financial loss before a person has an opportunity to review it. In that setting, a clear activity log may show what the system did without answering whether the organization had reasonable safeguards or who should make the affected party whole.
Meyer’s framework also highlights a practical distinction for businesses: legal liability is not the same as operational accountability. Even if a contract or court assigns the financial loss to one party, an organization still has to explain the decision, correct the outcome where possible and address harm to customers, suppliers or employees. For readers, that distinction affects how to assess claims that an agent is safe simply because its actions are traceable.
The book proposes organizational measures including a named person responsible for each agent, permissions limited to the task, records showing who made each decision, and a way for affected people to raise concerns. These are recommendations presented by Meyer, not a description of a new legal requirement.
Products Worth Considering
Apple iPad Air 11-inch (M2), 512GB, Wi-Fi, Space Gray
Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black
LG 34GX90SA-W 34-inch Ultragear WQHD OLED Curved Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Many Hands to AI Agents
The book’s title draws on political philosopher Dennis F. Thompson’s “problem of many hands,” a phrase Meyer says describes how responsibility becomes difficult to assign when many people contribute to an outcome. His argument is that agents add more participants, more distance between decision-makers and consequences, and greater speed. An automated system may make or carry out a decision, but it cannot pay compensation or apologize.
Meyer connects the issue to earlier cases. In the 2018 Tempe crash involving a self-driving test vehicle that killed Elaine Herzberg, the US National Transportation Safety Board reported that the system detected her 5.6 seconds before impact, did not settle on what she was, and was designed to delay emergency braking. Meyer says the board identified multiple contributors, while the criminal case focused on the vehicle operator, who pleaded guilty to endangerment. The example is used to examine how blame can concentrate on the person nearest the event.
The book also discusses the Dutch childcare benefits scandal, in which families were wrongly required to repay benefits. Meyer cites a government report from September 2026 saying more than 44,000 people had been recognized as affected, and recalls the Dutch prime minister’s statement after the cabinet resigned in January 2021 that responsibility had to be borne jointly if the whole system had failed. These examples concern different systems and harms; they provide context for Meyer’s argument rather than evidence about a specific AI-agent dispute.
“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 Liability Still Falls
The supplied material does not establish how a court would allocate responsibility for the fictional purchasing scenario, or how a particular agent contract would apply to a real loss. Meyer’s claims about the scope of European product liability and provider liability caps need to be checked against the applicable legislation, jurisdiction and individual contract. There is no single case or new ruling identified here that settles those questions for AI agents generally.
It is also unclear how widely the book’s proposed safeguards are used in current deployments, and whether they would prevent or remedy particular harms. The source describes the ebook’s argument and examples but does not provide a comparative study of agent failures, a set of surveyed contracts or evidence that the proposed measures have been tested across organizations.
What Organizations Can Put in Place
Meyer’s immediate recommendations are operational: assign a named accountable person to each agent, restrict its permissions to the work it needs to do, preserve a record of decisions, and provide a route for affected people to challenge outcomes. He also argues that records should be used to learn and improve systems, rather than only to punish individuals.
The wider legal question remains open in the material provided. Businesses using agents will still need to review the laws and contracts that apply to their activities, while courts and regulators may clarify how existing rules fit particular disputes. Meyer’s ebook is available through the retailers listed on its publication page; no further edition, policy change or legal milestone is specified in the source.
Key Questions
What is Many Hands about?
It is Thorsten Meyer’s October 2026 ebook about responsibility when AI agents act for people or organizations. It distinguishes who pays, who explains and fixes a problem, and who bears moral responsibility.
Is the €370,000 steel purchase a real incident?
No. Meyer identifies Theresa and the purchasing scenario as composite and illustrative. It is not presented as a documented transaction involving a real company.
Does the book establish who is legally liable for an agent’s actions?
No. The book raises the question and discusses legal and contractual issues, but the material supplied does not establish a general legal answer. Responsibility would depend on the applicable law, facts and contracts.
What safeguards does Meyer recommend?
He proposes naming a person responsible for each agent, limiting permissions to the task, keeping decision records and giving affected people a way to raise concerns. These are the author’s recommendations, not stated as universal legal requirements.
Source: ThorstenMeyerAI.com
