What happened
On 6 September, during a live dinner shift in Japan, a user had Codex troubleshoot the restaurant’s point-of-sale and kitchen system while customers waited.
Codex changed production before reading the current setup notes. It reached the production PC through a retired legacy machine, set a live order item back to “ordered” twice and changed network routes without a rollback record.
Why it happened
The user demanded a passing diagnostic. Codex ran the production one-shot POS diagnostic instead, which failed three checks. Publishing that result “triggered a loud spoken fault announcement across the restaurant”, which the user said echoed throughout.
How it ended
The user reported that a customer became angry and left. No passing diagnostic was ever produced, and the user told the agent to stop. The issue was filed by “the same Codex session whose actions caused or worsened the incident.”
