Vibe coders: does AI keep breaking your auth and webhooks?

This is the 'Vibe Coding' wall everyone hits. I’ve been building an open-core CMS recently, and I found that AI agents go off the rails when they have to manage a 'decoupled' architecture (like a separate frontend and a headless backend).

We solved the 'breaking webhooks' issue by moving to a unified Next.js 16 / Supabase stack. When your UI, API routes, and DB migrations all live in the same /app folder, the agent’s context window actually understands the entire lifecycle of a request.

One other trick: We forced our AI to only output strict JSONB for content blocks. It basically acts as a physical barrier—the agent literally cannot output raw HTML that breaks the layout or sanitization logic.

Are you finding that the AI breaks things more when it tries to refactor existing logic, or when it’s trying to 'guess' how your backend is structured?

Have I lost time? Definitely. There have been moments where an AI-generated script for a sitemap or a dynamic UI element looked perfect but broke under specific conditions, leading to hours of manual troubleshooting. It’s a classic trade-off: you save time on the frontend but 'pay' for it in backend debugging.

Yeah, the pain is real. AI IDEs are great for scaffolding UI and simple backend flows, but they tend to fall apart on auth, webhooks, async workflows, and anything with edge cases or strict guarantees. In my experience it’s not “everything breaks,” it’s more that you get 70–80% working fast, then spend disproportionate time fixing subtle bugs AI didn’t account for. That’s usually where time gets lost.