Skip to main content

Taxonomies

9 Critical Failure Patterns of Coding Agents

Columbia University DAPLab (blog post by Reya Vir) · v2026-01 · first published 2026-01-08

Scope

Nine failure patterns that the authors saw while building 15+ applications with five coding agents and vibe-coding tools (Claude, Cline, Cursor, v0, Replit; testing as of November 2025). The post says it documented "hundreds of failures" during development and grouped them into the nine patterns. It is a blog post about building web applications, not a peer-reviewed study, and it gives no counts per pattern.

Source → License: Blog post; no licence is stated on the page (checked 2026-11-21)

Why it's ingested

A first-hand account of where coding agents fail when building complete applications. Its patterns are about application quality (UI, state, business rules, data model, integrations), so only some of them have a counterpart among the SAICA failure modes; data/crosswalks/daplab-to-saica.yml lists which and gives a reason for each one that has none.

Categories & crosswalks

Each row is one category of this taxonomy with the SAICA failure modes mapped to it and how close each mapping is: “exact” means the same failure, “partial” an overlap, “related” a neighbouring category. 7 mappings cover 6 of the 9 categories; the 3 with no mapping are listed under them. The category ids and labels were last compared with the source on 2026-11-21.

Mapping drafted by an AI model from the source text; not yet reviewed by a person.

Categories with no SAICA failure mode

These 3 categories have no mapping. The reason is the one the crosswalk file states; where it states none, that is said.

Notes

Rebuilt on 2026-11-21 from the live post (HTTP 200, published 2026-01-08) and checked against the earliest Wayback Machine capture (2026-01-17), which lists the same nine headings. Labels are the post's own headings; quoted text in the descriptions is copied from the post. The ids DAP-01 to DAP-09 are SAICA-KG's, formed from the post's own numbering 1 to 9; the post publishes no identifiers. Retraction. Until 2026-11-21 this file held nine labels that are not in the post: Incomplete Task Execution, Fabricated References, Stale API Usage, Cascading Error Recovery, Context Window Overflow, Tool Misinvocation, Silent Test-Passing Workaround, Destructive Action and Goal Drift. The file's own note called them "paraphrased for seed" and asked for a check that was not done. The post does not describe agents editing tests, running destructive commands, claiming completion with work undone or fix attempts that add new errors. The same ids therefore now name different, real patterns; anything that cited an old DAP id by meaning must be re-read. The correction was first made on 2026-08-18 (commit 00422e2) and was lost when the branch was reset on 2026-11-19. Five incident nodes built on the invented labels were retracted; see data/TOMBSTONES.yml and archive/retracted-incidents/README.md.

View raw YAML on GitHub →