Can you vibe whatRust?

Unofficial Rust and Tauri desktop wrapper for WhatsApp Web, with persistent sessions, tray controls, notifications, and isolated accounts.

VISIT WEBSITE ↗

THE DECISION CONTEXT IMPLEMENTATION PROMPT TRADE-OFFS

CATEGORYBusiness Productivity

STARTING PRICEFree

FREE TIERFree, MIT-licensed source and GitHub release downloads

VIBE-CODE RATINGYES · 3 / 9

STATUSactive

TYPEopen_source_product

SOURCEOfficial pricing recorded

LAST CHECK2026-10-11

THE DECISION

YES · 3 / 9

The small desktop-shell version of whatRust is a good AI-assisted build candidate, not a plan to recreate WhatsApp. Use Rust and Tauri v2 to load only the official WhatsApp Web origin in the system webview. First build a single account with persistent login, close-to-tray, show/hide shortcut, saved window bounds, native notifications, and external links opening in the default browser. Use explicit media and download permission flows, keep remote web content isolated from privileged Rust commands, and never log messages, session cookies, or tokens. Test QR login, restart persistence, logout, denied permissions, downloads, external URLs, and tray behavior on each OS. Add multi-account storage isolation and app lock only after the single-account loop is reliable. WhatsApp provides the actual messaging network; calling, web compatibility, account policies, platform integration, signing, and upgrades remain dependencies. A useful wrapper is approachable, while full current whatRust feature parity requires more engineering.

OFFICIAL OPEN-SOURCE ALTERNATIVE

RUN THE CORE YOURSELF

whatRustUnofficial Rust and Tauri desktop wrapper for WhatsApp Web, with persistent sessions, tray controls, notifications, and isolated accounts.VIEW REPO IT →

Use or study the existing MIT-licensed Rust/Tauri wrapper. It already handles a WhatsApp Web desktop shell and documents platform-specific session, permission, call, and download limits.

COPYABLE IMPLEMENTATION PROMPT

Build an independent, original personal workflow inspired by whatRust.

Core context: Unofficial Rust and Tauri desktop wrapper for WhatsApp Web, with persistent sessions, tray controls, notifications, and isolated accounts.

First propose a secure, small first version. Include the core user flow, data model, permissions, failure states, and tests. Do not copy whatRust's branding, assets, proprietary data, or paid integrations.

OPEN IN CHATGPT ↗OPEN IN CLAUDE ↗OPEN IN CURSOR ↗

Opening an AI app also copies this prompt as a fallback.

THE USEFUL CORE

What AI can build

The small desktop-shell version of whatRust is a good AI-assisted build candidate, not a plan to recreate WhatsApp.
Use Rust and Tauri v2 to load only the official WhatsApp Web origin in the system webview.
First build a single account with persistent login, close-to-tray, show/hide shortcut, saved window bounds, native notifications, and external links opening in the default browser.
Use explicit media and download permission flows, keep remote web content isolated from privileged Rust commands, and never log messages, session cookies, or tokens.
Test QR login, restart persistence, logout, denied permissions, downloads, external URLs, and tray behavior on each OS.

WHAT REMAINS PAID

What remains paid

The personal workflow may be buildable, but polished integrations, team features, service reliability, support, and proprietary product advantages remain outside a small independent build.

QUESTIONS

What should I verify first?

Start with the official source, current terms or licence, practical setup requirements, and the limits of the recorded catalogue data.

Is this information current?

Last recorded check: 2026-10-11. Verify time-sensitive details with the linked official source.

Can I save this route?

Yes. Create an account or log in, then use the Save button to keep it in your collection.