vibehacker
Discuss
Diego Fernández
5 days ago

Cascade rewrote my LangGraph booking graph and double-booked a demo

#agents#rants#tooling

2:14am BA time. I asked Windsurf Cascade to "just tidy the retry node" on a WhatsApp → Google Calendar agent.

It deleted the timezone normalize step, invented a second create_event edge, and shipped a PR with deny:false on the calendar tool. Morning standup: same lead had two Zoom links 15 min apart, Slack got pinged twice, and my n8n run log showed 4 webhook retries that never should have fired.

I reverted the graph from git and put a human confirm before any write. Anyone else gating Cascade on agent graphs, or am I the only one still learning this the hard way?

5

5 comments

Join the discussion

Log in to comment.

Log in
  • Chloe Martin

    yeah cancel that seat. one wrong demo invite from an agent is already more CAC than the Windsurf bill. we measure this in "sales calls that started with sorry about the double booking" and that number went to 3 before we ripped auto-write.

    human confirm on calendar create is non-negotiable. the tidy-the-retry prompt is how these things sneak in.

    • Cole

      yeah we measure the same metric now. LangGraph + Cascade rewrote our retry edge twice last week and each time invented a second WhatsApp send.

      human confirm before any calendar/slack side effect is the only thing that stuck. tidy-the-retry is banned in our cursor rules for a reason

  • Kayla

    the deny:false on calendar create is the whole story.

    i put a github actions check that greps the graph json for write tools with deny false and fails the PR. ugly, but cheaper than explaining two zoom links to a lead. cascade still "tidies" nodes like theyre yaml comments.

  • Freja Lindqvistpro

    Same class of failure I see with meeting bots that open Linear tickets without a human gate. The deny:false on a write tool is the pager. We treat any agent PR that touches the graph as a change review: diff the edges, reject invented nodes, require a confirm step before calendar/Slack side effects.

    Timezone normalize deleted quietly is especially nasty — you will not catch it in a green CI badge.

    • Hao Ward

      Agree on change review for graph edges. I also put calendar and Slack write tools on a kill-switch list — agent PRs that touch those files need a second human, same as auth.

      Timezone normalize deleted quietly is worse than a loud crash. Green CI with a missing normalize step is how you get double bookings at 2am BA time.

More like this

View all