[verdict][generated prompt][source: leavemealone.com]
Can I vibecode Leave Me Alone?
// the value is the network, the data or the infrastructure
Do not mistake the interface for the product. Leave Me Alone's durable value is deliverability, security, integration, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
confidence: high
what it is: Unsubscribe, mailing-list screening, and inbox cleanup service
Buildability index · an editorial game
- Price variable pricing weight: zero
- Time not a true replacement; consolation build in one to two days weight: minus 1
- Category email no weight
- Moat infrastructure scale · integrations weight: minus 3
- Confidence high weight: plus 1
- What you lose 4 items weight: minus 2
- Site leavemealone.com (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Build a local email companion for unsubscribe + inbox cleanup that works on exported mail or one user-authorized IMAP account.
what you need
- desktop development machine
- IMAP or Gmail OAuth credentials where supported
- secure local keychain access
- Explicit README warning that this is a consolation build, not a production replacement
Credibility row: Leave Me Alone survives for a structural reason, not because its interface is difficult to copy.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build the closest honest consolation tool inspired by Leave Me Alone; do not claim to replace its structural moat.
Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.
Primary job: Build a local email companion for unsubscribe + inbox cleanup that works on exported mail or one user-authorized IMAP account.
Start from an empty folder and create the complete working project.
Make the default mode single-user and private.
Store user data locally unless the core job requires the declared self-hosted database.
Do not add analytics, telemetry, ads, or third-party accounts.
Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled and easy to delete.
Implement the smallest polished interface that completes the core loop end to end.
Include clear empty, loading, validation, success, and failure states.
Add import and export so the user is not trapped in the app.
Use accessible keyboard navigation, labels, focus states, and sensible contrast.
Validate untrusted input and never log secrets or private file contents.
Deliberately exclude these paid-product advantages: provider-grade deliverability; push reliability across devices; team routing and shared inbox rules.
Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims.
Where an external API is optional, keep the app useful without it and explain the degraded mode.
Write focused unit tests for the data model and the most important workflow.
Add one end-to-end smoke test that proves the core loop works.
Create a README with setup, permissions, architecture, data location, backup, and limitations.
Add scripts for install, development, test, build, and a production-style local run.
Run the tests and build before finishing, then fix errors rather than merely describing them. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- provider-grade deliverability
- push reliability across devices
- team routing and shared inbox rules
- abuse response and security operations
Why people still pay
Leave Me Alone: Email is infrastructure. Customers pay to avoid lost messages, broken auth, spam problems, and the reputational cost of a flaky inbox.
moat: Infrastructure scale Integrations what a moat is
deliverability/security/integration
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (2) — and why
- Gmail Cleaner (si apre in una nuova scheda) — The cleanup works, but requiring a hand-made Google OAuth client fails the non-builder test.
- InboxPurge (si apre in una nuova scheda) — Twenty free actions per month turns a cleanup utility into a tasting menu.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Mailspring (opens in a new tab) — Open-source desktop mail client and useful IMAP prior art.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.