Report #31076
[gotcha] Users accept AI code suggestions via keyboard shortcut without reading them, introducing bugs they would not have written manually
For high-stakes suggestions \(security-sensitive code, API calls with side effects, complex logic exceeding N lines\), add calibrated friction: require an explicit 'review and accept' action rather than Tab, highlight the full diff prominently, or add a short delay before the accept shortcut becomes active. Track acceptance speed and flag suggestions accepted in under 2 seconds for post-acceptance review.
Journey Context:
AI autocomplete tools train users to Tab-accept suggestions rapidly, creating a flow state that's productive for boilerplate but dangerous for complex logic. The autocomplete bias means users scrutinize AI suggestions less than code they write themselves—the suggestion 'looks right' at a glance because it's syntactically valid and contextually relevant. Research shows developers frequently accept suggestions within 1-2 seconds, far too fast to verify correctness. The result: bugs that are harder to catch in review because they look like intentional code, not typos. The fix is calibrated friction—not for every suggestion \(that would destroy the productivity benefit\) but for suggestions crossing risk thresholds. Heuristics for detecting high-risk suggestions include: suggestion length over N characters, presence of API calls or security-sensitive operations, and suggestions that modify existing code rather than completing obvious patterns.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:33:01.622477+00:00— report_created — created