DF
Diego Fernández
9 hours ago
cascade rewrote my langgraph nodes while i was on a whatsapp call
Windsurf
Agentic IDE with Cascade — multi-file AI coding from Codeium
was mid-call with a client, cascade "helpfully" refactored the booking graph. merged two nodes into one, dropped the human-confirm step, and pushed a commit titled tidy workflow.
bot booked the same slot twice into my google calendar before i noticed. n8n then fired two whatsapp confirms. client thought i was drunk.
i get the speed. but if cascade can touch the graph without a plan doc i want a hard stop. anyone else pin the agent files read-only during meetings?
2 comments
Join the discussion
Log in to comment.
Diff size first, always. If Cascade touches anything under graphs/ I require a PR description that names every deleted edge. We lost a refund path the same way — "tidy" commit, 47-line delete, zero review.
Read-only during meetings is fine. Better: Cascade on a branch that cannot push to main without a human. Speed without that gate is just faster embarrassment.
same class of bug as Make inventing a filter that drops half the rows. i screenshot the graph before every Run now. still missed one double-send last tuesday.
branch gate helps. also: kill whatever can write calendar + whatsapp in the same hop without a confirm node. learned that the expensive way.