The Ghost House Effect: Five Failure Modes in AI-Generated Code

The Ghost House Pattern

Developers report a consistent pattern when using Claude AI for coding: 10x speed improvements for the first 2-3 weeks, followed by a tipping point where technical debt compounds faster than refactoring can address it. The result is developers spending 8 hours daily "begging the agent not to break what it built yesterday."

Five Specific Failure Modes

• Shadow Dependencies: Claude imports libraries not in package.json. Code works locally but fails in CI/CD when the cache isn't present. Developers call these "AI ghost deps."
• Context Window Paralysis: As repositories grow, the agent starts summarizing and loses the big picture. This leads to fixes that accidentally break unrelated components, like nuking database migration scripts while fixing UI bugs.
• The Fear of Editing: Developers stop touching their own code because the architecture becomes so brittle that manual edits cascade into total failure. The mental model resides in the agent rather than the human developer.
• Hallucinated APIs: The AI invents internal endpoints or security libraries that don't exist. Code looks perfect in sandbox environments but returns 404 errors in production, creating "phantom" functionality.
• Architecture Drift: "Vibe coding" leads to "prompt-spaghetti" documentation. By month two, repositories become unmaintainable, requiring total rewrites for human developer onboarding.

The source notes that many founders reach a breaking point where they "had to nuke it and rebuild from scratch." The paralysis threshold appears to be hitting projects earlier in development cycles.