Why Vibe-Coded Apps Script Turns Into Trash After Three Months
Why quickly vibe-coded Apps Script projects become maintenance problems after the first successful demo.
5 posts
Why quickly vibe-coded Apps Script projects become maintenance problems after the first successful demo.
AI built me a field-inspection app on GAS. The demo ran fine. Then one deploy button locked out every field worker, Sheets swapped my text for a date, and a green checkmark lied. The tiny bugs I fixed all day — and what to watch for before you vibe-code on GAS.
Pasting code into a ChatGPT window isn't vibe coding. You want an agent that reads your files, runs your commands, and deploys — Claude Code or Codex, logged in over OAuth and running locally. A comparison table, setup, a real first session, approval modes, cost, and troubleshooting.
AI gave you a gorgeous front end. It only runs on localhost:3000 — a screen only you can see. Per-framework build folders, deploying to Cloudflare (static/SPA) and GAS (Sheets-backed), the 'works locally but breaks deployed' traps, and custom domains — commands included.
Wire an AI coding agent into clasp, Cloudflare, and gws-cli and you can mass-produce small owned tools at near zero cost, auto-deployed. A 5-minute example (form→sheet→email), the auto-deploy script, real cost numbers, the traps, and where a human must stay in the loop — no secrets held back.