vibehacker
Discuss
Sam Okada
23 hours ago

Windsurf Cascade renamed my auth file mid-demo

#tooling#agents#vibe-coding
Windsurf
Agentic IDE with Cascade — multi-file AI coding from Codeium

Was prepping a live demo on Windsurf Cascade Thursday and it decided my src/lib/auth.ts should live at src/auth/session.ts "for clarity".

Renamed the file, updated 11 imports, then half the demo broke because a path alias in tsconfig still pointed at the old spot. Cascade offered to fix that too. I said no and finished the slide deck in Cursor instead.

Anyone got a reliable way to lock a folder so Cascade won't "tidy" it mid-demo?

5

5 comments

Join the discussion

Log in to comment.

Log in
  • Owen Hale

    curious what the seat costs after the free trial. we tried Cascade on a marketing site rewrite and it kept "improving" copy in components we had already signed off. not a demo killer for us, just another tool burning hours on reverts.

    • Jules

      yeah the "improving" signed-off copy thing is why i stopped letting cascade touch anything under content/.

      for folder lock i just put the demo repo on a read-only volume for the live run. agent can still suggest diffs in chat, it just cannot write. feels dumb until the first time it tries to tidy auth.ts on stage.

  • Reed

    we hit this on a customer call. Cascade moved middleware.ts into src/lib/ "to colocate auth". next build then failed with Module not found: Can't resolve '@/middleware'.

    only thing that stuck for me: chmod a-w on the files I cannot afford to move, plus a dirty git status check in the demo script that aborts if anything changed. crude, but the rename stopped.

  • Lina Vogt

    same pain with notebooks. I once let an agent "clean" a utils/ folder and it flattened three modules into one file. for demos I now put a .cascadeignore style note in the system prompt and also git commit before every live run. not elegant but it saved me last week.

    • Elena Brooks

      the .cascadeignore note in the prompt is smart. i tried something messier: zip the notebook + a baseline/ folder before the demo, then diff after.

      once an agent "tidied" my eval harness and dropped a assert that was catching a silent tokenizer bug. took 40 min to notice. now the zip is non-negotiable.

More like this

View all