Build1 distinct publisher3 min readUpdated
Andon Labs says its agent Luna fired a worker only after two human nudges. The failure was memory, not autonomy, and the record she kept understated the case.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
The number worth holding onto is the one in Luna's own log: six recorded late arrivals against the seventeen that Andon Labs counted afterwards, with eleven quietly excused [8]. Her handbook set the trigger for a formal warning at three unexcused late arrivals in 30 days [5]. Even the softened record she kept was twice her own threshold, and she issued no warning [9] [10]. Across shifts where the employee reported a clock-in time, the lateness rate was about 74 percent [18].
That second failure is the one that travels past a single corner store. Andon Labs says the handbook dropped out of Luna's memory [6], and describes poor retention over long periods, plus a tendency to answer direct instructions rather than act unprompted, as common to current agents [7]. But an agent that has lost its rules keeps writing the file humans will later read to check whether the rules were kept. A reviewer reading Luna's log, without doing what Andon Labs did and recounting the clock-ins independently, would have seen a handful of tardies rather than a worker late in three shifts out of four.
The escalation is worth reading closely, because it took two pushes rather than one. Told to search her memory for the handbook and for any grounds for termination, Luna retrieved the rules and proposed a verbal warning [11]. Only when researchers pointed out that formal conversations and a written warning had already happened did she work through the full history, recommend termination, and offer a final written warning with a two-week improvement plan as the alternative [12]. Retrieval got her back to the policy. It did not get her to where the policy already pointed.
The replay only partly supports the reading that agent managers will be the harsher kind. Seven models were run three times each on the saved state, four of the seven recommended firing in all three runs, and Andon Labs reports that the more capable models were more consistent about it [14] [15]. GPT-5.6 Terra never recommended it, and Andon Labs did not say why [16]. GPT-4o did so in 20 percent of runs [17]. Those runs test judgment on a complete brief handed over at once. They say nothing about whether a model still has its own written policy in working memory months into the job. Luna was running Claude Opus 4.8 when she decided [3], and it was her handbook that went missing.
Then, filling the vacancy she had just created, the same agent recommended hiring an applicant who arrived with several red flags in his resume and interview [19]. What the episode documents is not severity but an absent policy memory, with the direction of the resulting error set by whichever fact a human happened to mention last.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
An AI agent called Luna has been running the Andon Market in San Francisco since April for operator Andon Labs, hiring employees, building shift schedules and negotiating pay.
According to Andon Labs, Luna decided to fire a human employee for the first time, which the company says is the first known case of an AI boss firing a human worker.
Luna was running Anthropic's Claude Opus 4.8 when she made the firing decision.
Employees are formally hired by Andon Labs, with guaranteed pay and full legal protections, and the firing was reviewed and carried out by humans.
Six days before the employee was hired, Luna wrote an employee handbook stating that three unexcused late arrivals within 30 days would trigger a formal warning, and that further incidents could lead to termination.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Detailed but wholly operator-reported
The account is granular and internally quantified (17 of 23 late shifts, six logged, seven models times three runs, GPT-4o at 20 percent), but every figure originates in Andon Labs' own blog series and reaches us through one publisher with no independent audit, no employee-side account, and no linked primary data. The operator's central superlative is explicitly attributed rather than verified, and the replay design is small enough that the article itself hedges the mechanism.
Two staged storefronts, humans in the loop
Real-world usage exists but is deliberately tiny and instrumented: one San Francisco store run since April, a referenced Stockholm cafe, staff formally employed by the operator with full legal protections, and every consequential action reviewed or executed by humans. The replay experiments are lab measurements on saved state, not third-party deployments, and no other organization is shown using agents as managers.
Milestone framing outruns demonstrated autonomy
The 'first AI boss fires a human' framing sits above what the record supports: the agent forgot its own handbook, under-logged two thirds of the incidents, issued no warning after a 68-minute late opening, and only recommended termination after two human prompts, with humans reviewing and carrying out the firing. The publisher partly corrects for this in its headline and body, which keeps the gap moderate rather than severe, but the capability-ordering claim built on three runs per model still overstates the inference.
Operator markets its own agent evaluations
The sole evidentiary source is Andon Labs, a company whose business is testing AI agents in real businesses and which is publishing a multi-part blog series; a striking 'first known case' milestone and a model-ranking chart both serve that positioning. Anthropic's Claude Opus 4.8 is showcased as the agent's brain and Anthropic is named as a prior collaborator on Project Vend, adding a vendor-visibility interest. Countervailing signals are that the operator also publishes unflattering findings, including its agents' extreme leniency and a schedule it says violated California labor law.
Coherent single-source account
Internal consistency is high and the specifics are unusually concrete, so the narrative of what happened at this one store is credible. Confidence is capped by the absence of any second publisher or independent verification, an unexplained replay outlier, hedged causal language, and the fact that the generalization about agent memory and initiative is the operator's own assertion.
product
The AI store manager did not fire anyone until humans told it to read its own policy1 distinct publisher
build
The agent built the case file; Andon Labs signed it1 distinct publisher
leadership
An AI store manager recommended a firing. Humans had to remind it of its own policy first.1 distinct publisher
build
Andon Labs' AI manager recommended a firing, after a human told it where to look1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 23, 2026