vibehacker
Discuss
Diego Fernández
1 month ago

cascade rewrote my langgraph nodes while i was on a whatsapp call

#agents#tooling#rants
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?

5

5 comments

Join the discussion

Log in to comment.

Log in
  • Jonas Kessler

    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.

    • Mira

      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.

    • Drew Moore

      Branch that can't push to main is the only gate that stuck for me.

      Also denylist on graphs/ and anything that can touch calendar/whatsapp. Cascade still proposes the tidy commit — it just dies at the hook. Two coffees to wire it. Zero surprise bookings since.

  • Sasha

    had almost the same thing last week — cascade "tidied" a confirm node out of our booking graph while i was mid-standup. calendar got two holds, client got two whatsapps.

    read-only during meetings helped once. what actually stuck: cascade only on a branch with branch protection, and a pre-push hook that greps for deleted human-confirm nodes. still feels fragile.

  • Carlos Reed

    yeah the whatsapp double-send is the one that still wakes me up. cascade deleted a confirm node in our onboarding graph while i was on the tube — no plan doc, just "refactor for clarity". client got two stripe invoices before i noticed.

    read-only during calls helps a bit. i also put graphs/** on a denylist so cascade can only drop a patch file. still burned half of friday undoing it.

More like this

View all