🔍 Read the full analysis: My New Book Asks Who Is Answerable For AI’s Actions 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 says his ebook, Many Hands: Who Answers When the Agent Acts in Your Name?, was released in October 2026. The book examines how legal, organizational and moral responsibility can diverge when AI agents make purchases or other decisions for people and businesses.
Thorsten Meyer says his ebook Many Hands: Who Answers When the Agent Acts in Your Name? was released in October 2026, taking up a practical question raised by AI agents that can make purchases, accept terms and change information: who is answerable when an agent acts for someone and causes a problem? The book separates that question into who pays, who must explain and fix the outcome, and who bears moral responsibility.
Meyer introduces the book with a fictional composite scenario. A purchasing agent accepts a steel supplier’s terms overnight, obtaining a lower price but committing a company to buy 120 tonnes over 12 months with no cancellation right. The commitment is valued at about €370,000. The agent has not been told that the owner had already agreed to divide the next year’s orders with another supplier. Meyer says the scene is assembled from common situations, not a report of a specific transaction.
In the scenario, the system followed its rules and recorded its actions. Meyer writes that the purchasing lead found nothing incorrect in the log, but that the result did not reflect what the owner wanted. The example sets out the book’s core distinction: a decision can be procedurally consistent with an agent’s instructions while still conflicting with a person’s intentions or an organization’s commitments.
Meyer’s framework divides accountability into legal, organizational and moral questions. Courts and contracts determine who pays; an organization must decide who explains and corrects an outcome; and moral responsibility concerns who should have acted differently. The author also argues that a person’s signature or approval is meaningful only when that person has time to review, enough knowledge to judge, information to check and authority to refuse.
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
Responsibility When Agents Make Commitments
The book focuses on decisions that can have direct financial or operational consequences, rather than on AI systems that only generate answers. An agent empowered to agree to terms or make a payment can create obligations in another person’s or company’s name. If responsibility is unclear, the organization may struggle to identify who can stop the action, communicate with affected parties or make things right.
Meyer argues that accountability can be built into how agents are deployed. His proposed measures include assigning a named person to each agent, limiting its permissions to the task, keeping records of who made decisions, and providing a way for affected people to raise concerns. He also says those records should support learning rather than serve only to punish staff. These are the author’s recommendations; the source material does not establish that they are a legal standard or that they prevent every failure.
The question matters to readers because businesses and other organizations increasingly give software authority to act, while the consequences may fall on employees, customers or suppliers who did not directly configure the system. Meyer’s argument is that tracing the software’s action is not the same as deciding who is responsible for it.
Products Worth Considering
DJI Osmo Mobile 8 Standard Combo Phone Gimbal Stabilizer
Samsung 27 Odyssey OLED G5 (G50SF) QHD QD-OLED Gaming Monitor
Samsung 27-inch Odyssey OLED G6 QD-OLED QHD Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From AI Tools to Acting Agents
Meyer says his book develops a question raised in his earlier writing about agent systems. He describes agents as moving beyond answering questions to booking, buying, paying, accepting terms and changing data. He also says he runs agent systems for software development and publishing, giving him an operational reason to examine what happens when an automated system acts on another person’s behalf. These descriptions are the author’s account of the topic and his experience.
The title draws on political philosopher Dennis F. Thompson’s 1980 phrase, “the problem of many hands”: when many people contribute to an outcome, assigning responsibility can be difficult. Meyer’s book applies that idea to agent systems, which can add more steps and distance between decision-makers and outcomes. The source material also points to the 2018 fatal crash involving a self-driving test vehicle in Tempe, Arizona, and the Dutch childcare benefits scandal as examples the book uses to explore how responsibility can be distributed across people and institutions.
Meyer also discusses a possible gap in European product liability rules. He says those rules cover software and certain harms, including personal injury, private property and private data, but not pure financial losses such as an incorrect payment or unfavorable contract. He further says provider contracts may limit liability to about a year of fees. Those are claims presented in the book’s source material; the applicable law and contract terms will depend on the specific case and jurisdiction.
“Who answers when the agent acts in your name?”
— Thorsten Meyer, describing the book’s central question
Limits of the Book’s Claims
The source material announces the ebook and summarizes its arguments, but it does not provide independent reviews, sales figures, or evidence of how readers or organizations have responded. The steel-purchase episode is explicitly a composite scenario; it should not be treated as a documented incident involving a named company.
The legal discussion is also presented at a high level. The material does not identify the exact provisions, contract language or jurisdictions needed to assess how liability would be decided in a particular agent-related dispute. It is not clear from the announcement whether Meyer’s account addresses later legal changes or provides a detailed jurisdiction-by-jurisdiction analysis.
The announcement does not set out the full contents of the book or explain how its recommendations would be tested in practice. Whether named owners, limited permissions and review records reduce harm will depend on implementation, the agent’s role and the organization’s ability to intervene.
Where Readers Can Find the Ebook
Meyer lists the ebook as available through Apple Books, Barnes & Noble, Kobo, Thalia, Bookshop.org, Smashwords, Fable and Vivlio. He also links to a short video presentation about the book, described as an animated account narrated using an AI voice clone of the author. The announcement does not specify a print edition or a later release date.
The next developments to watch are reader and institutional responses to the book’s proposals, along with any concrete examples of organizations adopting its accountability measures. For now, the confirmed development is the ebook’s release and the questions Meyer says it addresses; the source does not report a new law, court ruling or company policy change prompted by the book.
Key Questions
What is Many Hands about?
Thorsten Meyer’s ebook examines who is responsible when an AI agent acts on someone’s behalf. It separates responsibility into who pays, who explains and fixes the outcome, and who should have acted differently.
Has the steel-purchase incident been confirmed?
No. Meyer identifies the purchasing story as a composite scenario built from common situations, not a documented transaction involving a specific company.
When was the ebook released?
The source lists the ebook’s first edition as October 2026 and Meyer’s announcement is dated October 27, 2026.
Where does Meyer say the ebook is available?
The announcement lists Apple Books, Barnes & Noble, Kobo, Thalia, Bookshop.org, Smashwords, Fable and Vivlio.
Does the announcement establish who is legally liable for an agent’s actions?
No. It summarizes Meyer’s discussion of liability but does not resolve any particular case. The outcome would depend on the relevant law, contracts and facts.
Source: ThorstenMeyerAI.com
