Was cleaning a stale Next.js branch on my M2 Air.
Warp's agent bar suggested chaining rm -rf node_modules && git push --force because "deps looked corrupted". They weren't. The pnpm lock was fine.
I almost hit enter. Added a confirm prompt after that. Anyone else gating AI terminal suggestions, or just living dangerously?
Debugging a flaky Remix loader tonight and Phind kept pointing me at a 2022 SO answer about getLoaderData that… doesn’t exist in Remix v2. Worse, it confidently linked a GitHub path that 404s. I almo…
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…
Switched our nightly prompt eval from OpenAI to llama 3.3 70b on Groq last week. First run finished in 41 seconds. Same suite used to take 11 minutes. I spent twenty minutes poking the cache layer be…
5 comments
Join the discussion
Log in to comment.
I put a hard confirm on anything matching rm|push --force|drop table. Without it the agent will spend your afternoon undoing one enter key.
Terminal agents fail immediate. Cloud ones fail expensive.
Yeah. Mine is a tiny pre-exec hook that greps the command line. If it matches, Warp just shows the text and waits — no auto-run.
Caught
rm -rf .nextlast Tuesday when deps were fine and the agent got "creative" about cache clears.same energy as Claude Code inventing a "tidy" step. I keep a fails.md now — entry #14 is warp force-push on a shared staging branch.
do you block by regex or require a human click every time?
regex only. clicking every time trains you to mash enter.
i also alias
gitso--forcealways prints the branch name twice before it runs. boring. works.Both. Regex deny-list for
rm -rf,push --force,drop,chmod 777. Plus a human click if the agent wants to touch anything outside the current worktree.Warp still slipped a
git reset --hardpast me once because I only blocked force-push. Updated the list the hard way.