Submit a failure
Got burned by an agent? Every accepted case is credited on the site and in the newsletter. Submissions are public GitHub issues and pull requests, so the whole history is open.
1. Quick: open an issue
Describe what you asked, what the agent did, and why it was wrong. Anonymize code. A maintainer turns good cases into patterns.
Open prefilled GitHub issue ↗
Opens github.com in a new tab. Nothing is sent until you press Submit there.
2. Full: open a pull request
Each pattern is one YAML file in content/patterns/. This button opens GitHub's editor with the template prefilled; GitHub will fork the repo for you.
Open prefilled pull request ↗What makes a good submission
- A real case you saw, or a link to a public report. No invented numbers or quotes.
- Exactly one type: wrong feature, bug, or overreach (see About).
- A minimal example: the prompt, the diff, or a transcript excerpt.
- A fix you have tried, or one you think should work (we mark which is which).
- Credit: who reported it and where.
Pattern file template
content/patterns/your-pattern-slug.yamlslug: your-pattern-slug # must match the file name
category: overreach # wrong-feature | bug | overreach
agents: [claude-code, cursor, codex, copilot]
tags: [keywords, people, would, search]
title:
en: Short title of the failure
zh: 中文标题
summary:
en: One or two sentences.
zh: 一两句话。
symptom:
en: What you see when it happens.
zh: 发生时你会看到什么。
why:
en: Why agents do this. Credit sources; no invented numbers.
zh: 智能体为什么会这样。注明来源，不要编数据。
example:
caption:
en: Illustrative, or link to the real case.
zh: 示意，或附真实案例链接。
lang: text
code: |
Paste a minimal (anonymized) diff, prompt or transcript excerpt.
rule: |
## Rule heading
- Concrete, checkable instruction for CLAUDE.md / AGENTS.md / .cursor/rules.
extras:
- ref: verify-skill # or scope-guard-hook, diff-budget-check, ... (see content/snippets.yaml)
sources:
- title: Where this was reported
url: https://example.com/your-source