🔍 Read the full analysis: When AI Uses Your Name, Who Is Responsible For Its Actions? on ThorstenMeyerAI.com
Get the little things that make your day 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 liability, organizational responsibility and moral blame can fall on different people when an AI agent acts for a user or business, while noting that key questions about financial losses and oversight remain unresolved.
Thorsten Meyer published Many Hands: Who Answers When the Agent Acts in Your Name? as an ebook in October 2026, examining who bears responsibility when an AI agent makes purchases, accepts terms or otherwise acts for a person or company. The book’s central argument is that who pays, who must explain and repair the harm, and who deserves blame may be different parties.
Meyer illustrates the issue with a purchasing-agent scenario: an agent accepts a steel supplier’s terms at 2:14 a.m., securing a lower price while committing a company to buy 120 tonnes over 12 months with no cancellation right. The commitment is valued at about €370,000. The company owner had previously agreed to divide the following year’s orders with another supplier, but the agent had not been told. Meyer says the scenario is a composite, not a report of an actual transaction.
In the story, the agent followed its rules and logged its actions, yet the outcome conflicted with the owner’s intentions. Meyer uses the example to distinguish legal liability, which concerns who pays; organizational accountability, which concerns who explains and fixes a problem; and moral responsibility, which concerns who should have acted differently. The ebook is available through multiple retailers, according to the author’s announcement.
The book also discusses the 2018 fatal collision involving an Uber self-driving test vehicle in Tempe, Arizona, and the Dutch childcare benefits scandal. These examples are used to examine how responsibility can concentrate on a nearby operator or become diffused across organizations and institutions. They are background cases in Meyer’s argument, not new events reported in 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 Decisions Become Commitments
AI agents can do more than generate suggestions: they can buy, pay, accept terms and change data on behalf of users. When those actions create a contract or financial loss, the consequences may arrive before a person has reviewed what happened. That makes the question of responsibility practical for businesses deploying agents, customers affected by their decisions and policymakers deciding how existing rules apply.
Meyer argues that a visible human signature or approval does not automatically settle who is responsible. A person may have little time, limited information or no real authority to refuse an agent’s action. Conversely, a system’s audit log may document what it did without showing whether the organization gave it suitable instructions or controls. The stakes include not only who absorbs a loss, but whether someone can challenge a decision and get it corrected.
The announcement also describes a potential gap in European product-liability rules: as Meyer characterizes them, they cover software-related injury and damage involving private property or data, but not pure financial loss, such as an incorrect payment or unfavorable contract. That claim points to an area readers may want to follow, though the announcement does not provide a legal analysis of particular cases or jurisdictions.
Products Worth Considering
BowFlex SelectTech 840 Adjustable Kettlebell
Withings Body Smart Wi-Fi and Bluetooth Body Composition Scale
Therabody SleepMask Blackout Eye Mask with Vibration
As an affiliate, we earn on qualifying purchases.
The Many Hands Behind an Agent
The title refers to political philosopher Dennis F. Thompson’s 1980 account of the “problem of many hands”: when many people contribute to an outcome, it can be difficult to identify who is accountable. Meyer says AI agents add distance and speed to that problem, while creating a nonhuman actor that cannot itself pay compensation or apologize.
One example discussed in the book is the 2018 Tempe crash that killed Elaine Herzberg. Meyer cites the U.S. National Transportation Safety Board’s findings that the vehicle’s system detected Herzberg before impact but did not settle on what she was, and that emergency braking was held back by design. The board identified multiple contributing factors. The vehicle’s safety operator pleaded guilty to endangerment, while the book asks how responsibility should be understood across the wider system.
Meyer also points to the Dutch childcare benefits scandal, in which tens of thousands of families were wrongly required to repay benefits. He describes it as an example of responsibility spreading across models, officials, courts and agencies, with individuals able to assume that another part of “the system” had checked. These cases provide a frame for the book’s discussion; the source announcement does not present them as new findings.
“Protects the integrity of the technological system, at the expense of the nearest human operator.”
— Madeleine Clare Elish, as quoted in Meyer’s announcement
Liability for Financial Loss
The announcement does not resolve how courts would allocate responsibility for a specific AI-agent transaction, or whether liability would fall on the user, the deploying business, the software provider or several parties. The steel purchase is a composite illustration, not a disclosed dispute with an identified supplier or company.
Meyer says European product-liability rules leave pure financial loss outside the categories he discusses, but the announcement does not identify a court ruling establishing how every agent-related loss would be treated. The terms quoted from model providers are described as capping liability at about a year of fees; the source does not name the contracts or show that this limit applies across providers.
It is also unclear what safeguards were used in any real deployments behind the examples, how often agents make comparable commitments, or what regulatory or legislative changes may follow. The ebook offers an argument and recommendations, not an announced change in law.
Controls Before Agents Act
Meyer’s proposed safeguards include assigning a named person to each agent, limiting its permissions to the task, recording who made each decision and providing a way for affected people to seek review. He also argues that records should support organizational learning rather than serve only as a tool for punishment. These are recommendations in the book, not requirements shown to have been adopted by regulators.
The immediate next step for readers and organizations is to examine the authority they give agents: what actions an agent can take without approval, what information it can access, and who can stop or reverse a commitment. The legal position will depend on applicable law, contracts and the facts of each case. Meyer’s ebook, published in October 2026, sets out his analysis; the announcement does not identify a related court decision or policy milestone due next.
Key Questions
What is Many Hands about?
Many Hands: Who Answers When the Agent Acts in Your Name? is Thorsten Meyer’s October 2026 ebook about responsibility when AI agents act for people or organizations. It separates the questions of who pays, who fixes a problem and who bears moral responsibility.
Is the steel-purchasing story a real case?
No. Meyer describes Theresa and the €370,000 steel commitment as a composite scenario built from common situations, not a reported real transaction.
Does the book say who is legally responsible for an agent’s actions?
The announcement does not give a single answer. It says legal responsibility can depend on courts and contracts, and distinguishes that issue from organizational duties to explain or repair an outcome.
What safeguards does Meyer recommend?
His recommendations include a named person responsible for each agent, permissions limited to its task, a record of decisions and a route for affected people to seek review. He also says records should help organizations learn from failures.
Has a new law or ruling settled the issue?
The source announcement reports no new law or ruling resolving responsibility for AI-agent actions. It describes Meyer’s concerns about financial losses and existing liability rules, while leaving the application to particular cases unsettled.
Source: ThorstenMeyerAI.com
