Your wallet now has a lawyer, and the lawyer thinks you’re lying.

Built in three hours. Won the Hexclave track at c0mpiled 13 — and sold it to six other people at the hackathon inside that same window.

Why it exists

Impulse buying is not a willpower problem. It is a design problem, and the design is not on your side. Modern storefronts are built by people who are extremely good at their jobs: urgency banners, one-click checkout, saved cards, recommended add-ons, free-shipping thresholds that make you spend more to save less. Every part of that funnel is tuned to compress the gap between wanting something and paying for it.

SwiperNoSwiping puts the gap back. It inserts about ninety seconds of friction at exactly the moment the funnel is trying to remove it, and fills that gap with someone asking why.

How it works

The content script scans the page for buy, checkout, and add-to-cart buttons and draws a transparent div on top of each one, so the click never lands. When you click anyway, a shadow-DOM modal opens.

Product context — title, price, a trimmed DOM snippet — goes to the backend, which supplies what it knows about you: your stated financial goals, the things you have actually said you want, your current financial position, and your recent purchase history. The model uses all of it to argue with you, and keeps going until it reaches a verdict rather than stopping after a set number of questions.

While that conversation is happening, it also goes looking. Using Channel3 product data, the agent researches real alternatives to the thing in your cart — cheaper options that still meet the need you described. Rather than only telling you no, it can tell you this other one does the same job for less, which is usually the more useful answer.

• Approved — the overlay is removed and the real button is clicked for you.
• Rejected — the attempt is logged, the price is added to your savings total, and that item gets a cooldown.

The savings counter matters more than it sounds. Money not spent is invisible, which is why it never feels like a win. Putting a number on it makes the avoided purchase as legible as the purchase would have been.

Deliberate constraints

Chrome only. No browser.*, no polyfill, no cross-browser shims. One AI provider, DeepSeek, routed through a single client module — every call in the project goes through it, with no fallback model.

The backend exists for exactly two reasons: the API key must not sit in a content script, and SQLite needs a filesystem. If the provider is unreachable the extension fails open rather than trapping you on a checkout page. A tool that blocks purchases is only acceptable if it can never block them by accident.