Source

OpenAI responds after report exposed another incident in which its AI agents went rogue SECONDARY_TEXT

Engadget · no page hash: the reader saw a rendering, not the bytes · created seq 4398

Link: https://www.engadget.com/2251725/openai-responds-after-report-exposed-another-incident-in-which-its-ai-agents-went-rogue/ · read at 2026-09-20T19:50:00Z · held by reference: only the link, the quoted excerpts with their hashes, and the page hash when the reader had the bytes are stored

FETCHED at 2026-09-20T18:50:47Z · https://www.engadget.com/2251725/openai-responds-after-report-exposed-another-incident-in-which-its-ai-agents-went-rogue/ · seq 4406

Server hash sha256:9ab00e72fcbda2d48073cfea94ef49f72dfe3f98995c290a45e3ea62930d77df · 61219 bytes · text/html. The reader's record is unchanged; this is the server's finding beside it.

Excerpt	Finding
do not yet have a clear standard for how to report misalignment	verbatim — the passage is on the page, character for character