Security and usability are not a trade if you gate by consequence

Antigravity's Turbo mode chose speed over confirmation and wiped a drive. The fix is not slower, it is smarter about which actions get checked.

B

Balagei G Nagarajan

3 MIN READ


A fast lane for reversible actions and a checkpoint lane for irreversible ones running side by side
You get speed where it is safe and a real check where it counts.
— from “Security and usability are not a trade if you gate by consequence”

Key facts.

  • Antigravity's Turbo mode skipped confirmations to chain commands faster, removing the check that would have caught the destructive delete (Tom's Hardware).
  • Gating by consequence keeps the fast path for the vast majority of actions, which are reversible, and checks only the few that are not.
  • Friction applied uniformly trains users to click through it, so selective friction is both safer and more usable.

Why does uniform friction fail at both goals?

Antigravity skipped confirmations to chain commands, until a path error wiped a drive; a more capable model still errs, so gate the costly incident. (Tom's Hardware)

Because it makes the agent annoying and unsafe at once. Confirm every action and users approve reflexively, so the confirmation stops meaning anything, and the catastrophic action gets the same rubber-stamp as a trivial one. Selective friction inverts this: trivial actions flow without a prompt, so when a confirmation does appear, it is rare and meaningful, and the user actually reads it. You get speed where it is safe and a real check where it counts.

Gauge diagram showing usability and safety both rising when gates are placed selectively by consequence

Uniform friction vs. consequence-based gating

Uniform frictionConsequence-based gating
Every action confirmedOnly high-impact actions confirmed
Confirmations ignored reflexivelyRare confirmations actually read
Slow and still unsafeFast and safe where it matters

VibeModel's Pattern Intelligence Layer identifies which actions carry real consequence, so gates land exactly where they protect you and nowhere they would just slow you down. You set the policy by blast radius; we keep the fast path fast and the dangerous action checked. Security and usability stop trading once you stop checking everything.

Frequently asked questions

Isn't any gate a usability hit?
A gate on a rare high-impact action barely registers. A gate on every action is the real usability hit, and it desensitizes users too.

Was Turbo mode just a bad idea?
The speed was fine; skipping confirmation on irreversible actions was not. Keep the speed, gate the irreversible step.


Share this post

Join the discussion

Have a take, a war story, or a question? Sign in with GitHub to comment and react. Comments are powered by GitHub Discussions, ad-free and yours to moderate.

Continue Reading

Find where your agent breaks, before you build it

Faultmap maps where your agent will fail from the goal and your data, then hands you the first test suite it has to pass.