Public incident reports for agentic oops

AI agents are just expensive while loops. Send oops.

A tiny museum of automation faceplants, runaway tools, token bonfires, and workflows that really should have asked a human sooner.

Infinite LoopTool Call Gone WrongBrowser Automation FailHallucinated ConfidenceToken BonfireHuman Had To Intervene

The wall

Latest approved oops from the loop mines.

Human Had To Intervene Funny

I yelled my OpenClaw… I never did it again

I yelled at my OpenClaw 🦞 agent. It wasn’t loading website on correct port or something. It told me to fuck off 🫠

Submitted by @agenticmarc

Submit safely

Your fail goes through GitHub review first.

The form opens a GitHub issue with structured fields. Submissions start as needs-review, then approved posts can be published to the wall. A GitHub account is required, which helps keep the queue reviewable.

Redact secrets, customer data, credentials, private company details, and screenshots that show anything sensitive. Funny is good. Leaking production is not.

Images are welcome. Paste or drag redacted screenshots into the GitHub form so the review queue keeps the receipts with the story.

Public references work too: news articles, X posts, TikToks, GitHub issues, videos, and blog posts from known platforms and recognizable sources. Link the source and add why it belongs on the wall.

You keep ownership of what you submit. By submitting, you agree it can be published and reused under Creative Commons Attribution 4.0 International, with attribution to your GitHub username unless you ask for a different credit.

Open the issue form

House rules

Laugh at the loop, not at private data.

Redact first

No API keys, tokens, customer names, internal URLs, or confidential screenshots.

Name tools carefully

Call out public tools when useful. Avoid doxxing teams, clients, or coworkers.

Keep it constructive

The point is better agent design, better evals, and fewer expensive loops.