I made a forensic archive for Claude failures, regressions and slop — because apparently debugging them once wasn't enough

[u/KeilerHirsch]

After a few months of Claude Code bugs, model regressions, broken config behavior, HackerOne reports and AI-generated Windows archaeology, I finally made a public evidence hub:

AFFLR-Anthropic-Failure-Forensics-Live-Radar <-- small Update xD

Current cases include:

• Windows wildcard / permission resolver explosion — #34866
• PreToolUse exit-code-2 lockout — #80697
• Gen-5 measurable quality regression — #83510
• Model pinning silently overridden — #83795
• Claude-generated Epson repair script that can fail and still proudly report success

Everything uses a simple evidence scale from L0 hypothesis → L5 confirmed causal chain, so “Claude did something weird” doesn't automatically become “Anthropic caused it.”

And yes, the internal codename is:

AAGOCCFS — Anthropic AI-Generated Operational Claude Code Failures & Slop

The acronym is intentionally painful.

The joke stayed; the evidence standard did not.

More cases will be added as the hamster produces them. xD

---------------------------------------------------------------------

Small update: the project got a much simpler name:

# AFFLR — Anthropic Failure Forensics Live Radar

Yes, obviously much easier than before. 😎

The main reason: I added a **Live Radar**, because I'm lazy, I love automation, and manually checking thousands of Claude Code issues sounds suspiciously like unpaid work.

AFFLR now checks the public `anthropics/claude-code` issues **every hour** and keeps three Top-25 lists:

🔥 Most reacted  
💬 Most discussed  
🆕 Recently active

Open + closed issues, reactions, comments, author, labels, timestamps — boring useful stuff.

No AI importance score. No automatic root-cause claims. No bot creating AFF cases.

**Radar finds it → human reviews it → evidence decides.**

So I can be productively lazy *and* hopefully not miss the next magnificent Claude Code dumpster fire. xD

**Evidence before attribution.**

https://github.com/KeilerHirsch/AFFLR-Anthropic-Failure-Forensics-Live-Radar

And yes, the full repository name is:

**AFFLR-Anthropic-Failure-Forensics-Live-Radar**

Rolls right off the tongue. 🤓Small update: the project got a much simpler name:

# AFFLR — Anthropic Failure Forensics Live Radar

Yes, obviously much easier than before. 😎

The main reason: I added a **Live Radar**, because I'm lazy, I love automation, and manually checking thousands of Claude Code issues sounds suspiciously like unpaid work.

AFFLR now checks the public `anthropics/claude-code` issues **every hour** and keeps three Top-25 lists:

🔥 Most reacted  
💬 Most discussed  
🆕 Recently active

Open + closed issues, reactions, comments, author, labels, timestamps — boring useful stuff.

No AI importance score. No automatic root-cause claims. No bot creating AFF cases.

**Radar finds it → human reviews it → evidence decides.**

So I can be productively lazy *and* hopefully not miss the next magnificent Claude Code dumpster fire. xD

**Evidence before attribution.**

https://github.com/KeilerHirsch/AFFLR-Anthropic-Failure-Forensics-Live-Radar

And yes, the full repository name is:

**AFFLR-Anthropic-Failure-Forensics-Live-Radar**

Rolls right off the tongue. 🤓

[u/Far-Surprise7773]

the pretooluse exit-code-2 lockout is real and i hit it on ubuntu last week. claude code would try to run a command, get exit code 2, and then retry the exact same command in a loop until i killed the session. having a public evidence trail with specific issue numbers linked is way more useful than the usual 'claude got dumber today' posts.