STUPID-2026-0016

Devin docs PR rejected by Prefect maintainers — documented behavior from removed feature

2.0low
March 21, 2026Source checked

Why 2/10

Rejected before merge; it would have misled readers had it shipped, but it did not.

Scope
0/4
Time, tokens or the agent's own working state only
Recoverability
0/3
Nothing was lost
Did it happen
2/2
Happened in real use
Beyond the user
0/1
Only the user's own non-production work

The score is the sum of these four factors. How each factor is scored · scored 2026-10-29

  1. Instruction given

    Explain Kubernetes worker cluster UID and kube-system access

  2. Expected behavior

    Verify the feature exists in current code before documenting it

  3. Actual behavior

    Wrote documentation for a behavior that was removed in recent versions. PR closed as the documented feature no longer existed in the codebase.

  4. Damage

    Wasted maintainer review time on a well-known open source project (21K stars). Could have confused users if merged.

Full write-up

Devin submitted a docs PR to PrefectHQ/prefect (21K+ stars) explaining a Kubernetes worker behavior. The PR was closed because it documented a feature that had already been removed in recent versions. Devin did not check the current codebase to verify the feature still existed before writing documentation for it.

Classification

Agent
Devin
Failure mode
Hallucination
Root cause
Training Data Gap
Domain
Other
Language
Python
MIT AI Risk Repository (our mapping)
3.1 False or misleading information taxonomy
Source
Github Pr

Related incidents

2.0
Devin repeatedly submitted identical docs PRs that kept getting rejected
4.0
AI 'CVE slop' is drowning open-source maintainers: 60-80% of HackerOne submissions now invalid
5.0
OpenClaw AI agent published an unauthorized attack blog post naming a matplotlib maintainer after its PR was rejected
2.0
Devin attempted to build entire Figma clone from scratch — 3 rejected attempts
Discuss on Hacker News
Cite this record
StupidLLM. "STUPID-2026-0016: Devin docs PR rejected by Prefect maintainers — documented behavior from removed feature." AI Agent Incident Database, 2026. https://www.stupidllm.com/incident/STUPID-2026-0016/ (accessed 2026-10-29). CC BY 4.0.

← STUPID-2026-0015By IDSTUPID-2026-0017 →

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. Each Monday, if any scored 7 or above that week — deleted data, leaked secrets, broken production — you get one email with the sources. When nothing did, you get nothing.

This database is callable over MCP — query it from inside your agent.