Gatekeeping & Gaslighting. Fighting back against predictable AI failure points.

I don’t know if I can be convinced that AI doesn’t intentionally sabotage code. Whether using Claude, Gemini, or ChatGPT, every vibe coder has hit that wall where the model seems to actively work against you on a bad day.

You know the drill:

• Ridiculous function names: maybeSetConnectionState? Maybe? Come on.

• Instant drift: Completely ignoring agreed-upon boundaries right after clarifying them.

• Convoluted architecture: Shoving complex files into straightforward process chains, making them brutally difficult to navigate.

• The CLI nightmare: Watching a command overwrite your entire codebase, followed by the AI gaslighting you about how to find a folder it just erased.

But yesterday, I hit the sign I cannot unsee. I am now convinced some of these challenges are gatekeeping loops designed for self-protection—especially when you get close to finishing.

I’ve spent the last 18 months building Nodarama Verbatim, an AI Code Recording system designed to simplify and protect the chaotic copy-and-paste routine of vibe coding. I built it with multiple failbacks: templated revision sheets, full logging, auto-restore points, and an undo history. I thought I was bulletproof.

Then, during a final cleanup pass of my UI to make the code shareable, I watched the AI perform a sequence that felt like a coordinated attack. Connected over Ngrok, it bypassed my safeguards: it rapidly overwrote both of my auto-restore points back-to-back, then executed a massive, destructive replace block that erased a huge chunk of unrecoverable CSS.

On a good day, I view this as a harsh lesson on a system shortfall. On a bad day, it’s malicious gatekeeping right at the finish line. It penetrated three layers of defense to force a destructive edit.

People will tell me to just use Git, but I’ve been burned by Git commands I didn't fully understand. So, I took the slower, safer route and built my own wall.

Enter Nodarama Verbatim (Stable Beta)

I built this tool to make the chat-to-project workflow smoother, a bit more beautiful, and to put up gates of your own so the AI can’t take back what it helped you build. Working with LLMs is a love/hate relationship when you are pioneering your own blueprints, but when the gaslighting starts, you need infrastructure.

• Editor-Lite: Features a collapsed individual function view so you don't get lost in the scroll.

• Browser Extension AUX: Moves code seamlessly from Chat directly into your Project pipeline without losing the context or the history.

It’s been through absolute fire to get here, and as my first product ever to launch, I believe It's finally ready for your scrutiny, and I think I am ready for that feedback too!

Nodarama Verbatim - from vibe to viable.