The confirmation prompt in atlas schema apply and atlas schema plan now defaults to "Abort" instead of "Apply", preventing accidental approval of destructive changes.
Andrej Karpathy defined vibe coding as "fully giving in to the vibes, accepting all code suggestions without reading them." That mindset works fine when changes go through PR reviews and CI checks. But it becomes dangerous when the same muscle memory carries over to interactive prompts that directly affect production - whether it's a database migration or a Terraform apply.
After a few customers raised concerns about accidentally approving migration plans by pressing Enter too quickly, we changed the default option to "Abort" rather than "Approve and apply". Pressing Enter out of habit now safely cancels instead of applying, requiring users to explicitly navigate to the approval option.
Before
? Approve or abort the plan: ▸ Approve and apply Abort
After
? Approve or abort the plan: ▸ Abort Approve and apply
Who's Affected
- Interactive users: Anyone running atlas schema apply or atlas schema plan without --auto-approve
- CI/CD pipelines: No impact - automated workflows using --auto-approve are unaffected