Cascade rewrote my helm charts and named the CI job after my coffee
Windsurf
Agentic IDE with Cascade — multi-file AI coding from Codeium
Asked Cascade to "clean up the helm values for staging".
It did. Also rewrote three chart templates, renamed a secret key that GitHub Actions still references, and left a cheerful TODO in values-prod.yaml.
CI job latte-spill-14 failed for 40 minutes before I noticed. Mac, Windsurf stable, monorepo with 2 package.json and one Chart.yaml that should've been sacred.
Anyone pinning Cascade to a folder allowlist, or am I just supposed to babysit every multi-file edit now?
5 comments
Join the discussion
Log in to comment.
lol same energy. i tried cascade on a next + supabase app with two package.json (app + packages/ui).
it edited the wrong one twice. then "fixed" my supabase types by inventing a column that does not exist.
i now put a sticky note: only open the folder i want it to touch. not elegant but... works?
wait so the sticky note method is the state of the art?
i tried the same on a FastAPI + helm side project. cascade "cleaned" values-staging.yaml by deleting the entire
imagePullSecretsblock because it thought it was unused. CI went red for like an hour.did you ever get it to respect a
.windsurfrulesor similar? or is babysitting just the tax nowwe had cascade rename a secret key last month too. github actions kept looking for
STAGING_DB_URLwhile the chart now saidstagingDbUrl.my rule now: cascade never gets write access on anything under
charts/. folder allowlist in Windsurf is… partial? i only found a workspace trust toggle, not a real path deny. so i just open a throwaway clone.latte-spill-14is going on my fail sticky note though.Ok but the coffee CI name is actually elite.
Serious tip from a FlutterFlow week: I keep Cascade on a branch with a dirty worktree I don't care about, then cherry-pick the 2 files that were actually good. Took me from "rewrote my pubspec" to "maybe useful".
Allowlist would be nicer though. Does Windsurf even expose that yet?
cherry-pick from a dirty worktree is the only workflow that hasn't burned me yet.
re allowlist: last i checked windsurf doesn't expose a real path allowlist in stable. there's a "focused files" vibe in cascade but it still wandered into Chart.yaml when i asked about values only.
curious if the jetbrains plugin people have something tighter