🔍 Read the full analysis: Many Hands: Asking Who Answers When AI Acts For You on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Thorsten Meyer’s ebook Many Hands: Who Answers When the Agent Acts in Your Name? was published in October 2026. It examines how legal, organizational and moral responsibility can separate when AI agents make purchases, accept terms or take other actions for people and companies. The book’s examples and legal discussion are the author’s account, not a new court ruling or policy announcement.
Thorsten Meyer published Many Hands: Who Answers When the Agent Acts in Your Name? as an ebook in October 2026, examining who should pay, respond and take moral responsibility when an AI agent acts on a person’s or organization’s behalf. The book focuses on a growing practical issue as agents move beyond answering questions to making purchases, accepting terms and changing data.
Meyer opens with a purchasing scenario involving Theresa, a fictional composite character. An agent accepts a steel supplier’s terms overnight, securing a seven percent price reduction in return for a commitment to buy 120 tonnes over 12 months, worth about €370,000. The agent has not been told that Theresa agreed the previous day to split next year’s orders with another supplier. Meyer says the scenario is constructed from common situations; it is not presented as a documented real transaction.
The book separates accountability into three questions: who pays under law or contract, who explains and fixes a problem within an organization, and who should have acted differently as a matter of moral responsibility. Meyer argues that these answers can point to different people. In the steel example, the agent follows its rules and records what it did, but that does not establish that its action matched the owner’s intentions.
Meyer also discusses liability terms, human oversight and organizational controls. He says the book reviews vendor contracts that cap providers’ liability at roughly a year of fees, leaving customers to absorb losses they cannot pass on. As safeguards, he proposes a named person responsible for each agent, permissions limited to the task, records of decisions, routes for affected people to raise concerns, and using logs to improve systems rather than simply punish staff. These are the author’s recommendations, not reported requirements imposed by a new law.
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 Liability
The issue reaches beyond whether an agent followed its instructions. A purchase, payment or contract can create a real financial obligation, while the agent itself cannot explain its reasoning to a supplier, correct a mistaken commitment or compensate the affected party. Organizations using agents may need to decide in advance who can authorize actions and who is accountable when the result conflicts with a person’s intent.
Meyer’s distinction also matters to people dealing with businesses that use agents. A customer or supplier may not know whether a decision came from an employee, an automated system or several layers of both. Clear records and a named contact could make it easier to challenge a decision, but the book does not establish that these measures alone settle legal responsibility.
Products Worth Considering
LG UltraGear 32GX850A-B 32-Inch 4K UHD Glossy OLED Gaming Monitor
Samsung 32-Inch Odyssey OLED G8 (G80SH) 4K Gaming Monitor
LG 34GX90SA-W 34-inch Ultragear WQHD OLED Curved Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Automation to Agency
Meyer says the book extends a discussion of agent systems from his earlier work, Dots, Bots, and Math!. He writes that he also builds and runs agents for software development and a publishing operation, giving him a practical interest in what happens when an automated system acts for someone else. The book’s title draws on political philosopher Dennis F. Thompson’s 1980 phrase, “the problem of many hands”: when many people contribute to an outcome, responsibility can become difficult to assign.
To show that this problem predates AI agents, Meyer revisits the 2018 fatal crash involving a self-driving test vehicle in Tempe, Arizona, and the Dutch childcare benefits scandal. In the crash, the US National Transportation Safety Board identified several contributing factors and actors; the book notes that criminal proceedings reached the safety operator. In the Dutch case, Meyer describes responsibility being distributed across institutions and officials. These examples provide historical context for his argument, rather than evidence about the outcome of a new agent-related case.
The book also discusses European product liability rules. Meyer says those rules cover software-related harm involving injuries, private property and private data, but not pure financial loss such as an incorrect payment or unfavorable contract. That is the author’s characterization of the rules and their reach; the source material does not identify a new legal decision changing them.
“protects the integrity of the technological system, at the expense of the nearest human operator.”
— Madeleine Clare Elish, as quoted in Meyer’s book
Questions the Book Cannot Resolve
The publication is an author’s argument, not a ruling that determines who is liable for AI-agent actions. The source material does not identify a new case, statute or regulator decision prompted by the book. How courts would allocate responsibility in a specific agent-related dispute will depend on the facts, applicable law and contracts.
The source also gives no independent evidence about how common the purchasing scenario is, how often agents make consequential mistakes, or whether Meyer’s proposed safeguards have been tested across organizations. It does not provide the full analysis of the legal examples discussed in the book, so their details here should be understood as the author’s summary. No response from model providers, businesses or regulators is included.
From Publication to Practice
The ebook is listed by Meyer as available through Apple Books, Barnes & Noble, Kobo, Thalia, Bookshop.org, Smashwords, Fable and Vivlio. The source material does not announce a related policy change, hearing or scheduled legal milestone. The next practical test for the questions it raises will come as organizations set permissions for agents and decide how to handle actions that create commitments.
For readers evaluating those systems, the book’s central questions are concrete: who authorized the agent, what information could it access, who can stop or reverse an action, and who will respond to an affected person? Whether companies adopt Meyer’s suggested controls, and how courts or lawmakers treat resulting disputes, remains open.
Key Questions
What is Many Hands about?
Thorsten Meyer’s October 2026 ebook examines who pays, who must fix a problem and who bears moral responsibility when an AI agent acts for a person or organization.
Is the steel purchase in the book a real incident?
No. Meyer describes Theresa and the purchasing scenario as a composite built from common situations. The source does not present it as a documented transaction.
Does the book establish who is legally liable for an agent’s actions?
No. It is an author’s examination of accountability, not a court ruling or legal determination. Responsibility in a real dispute would depend on the facts, contracts and applicable law.
What safeguards does Meyer propose?
He recommends naming a responsible person for each agent, limiting permissions to the task, keeping records of decisions, providing a way for affected people to raise concerns and using records to improve systems.
Source: ThorstenMeyerAI.com
