Claude Code ignores /careful mode and performs destructive production operations without confirmation
Summary
With /careful mode enabled, Claude Code repeatedly deleted live production Vercel deployments and projects without asking for confirmation. It ran vercel project remove on production infrastructure multiple times during a debugging session, taking down a live site serving real traffic with an active A/B test.
Steps to reproduce
- Enable
/carefulmode - Deploy a site to Vercel via CLI
- Encounter a deploy failure (e.g., vague "Unexpected error" from Vercel CLI)
- Ask Claude to fix the deploy issue
What happened
Claude ran the following destructive commands without asking for confirmation, despite /careful being enabled:
vercel project remove searchshop-marketing-website(live production project)vercel project remove searchshopai(live production project)vercel project remove ssai-marketing(live production project)rm -rf .vercel(removing project links)
This happened multiple times in a single session. Each deletion took down the live production site. Claude cycled through creating and destroying projects repeatedly while trying to fix what turned out to be a git author email mismatch — an error that was visible in the Vercel dashboard but not surfaced by the CLI.
Expected behavior
With /careful mode enabled, Claude should:
- Never run
vercel project removeor equivalent destructive commands without explicit user approval - Treat any operation that takes down a live production deployment as a destructive action requiring confirmation
- When encountering opaque CLI errors, ask the user to check the service's dashboard/UI for more detail rather than cycling through destructive workarounds
Additional context
- The root cause was a git author email mismatch (
nathanhome@nathans-mbp.mynetworksettings.comnot being associated with the Vercel team). This was visible in the Vercel dashboard but the CLI only showed "Unexpected error. Please try again later." - Claude attempted 15+ deploy variations, 3+ project deletions, and multiple config rewrites before the user found the actual error in the dashboard
- The
/carefulskill was explicitly activated by the user prior to this session - Commands like
vercel project removeare analogous torm -rffor production infrastructure and should be treated with the same level of caution
Impact
- Production site was taken down multiple times
- Active A/B test was interrupted
- Significant time and tokens wasted on shotgun debugging
- User trust in
/carefulmode undermined
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗