macOS
Coming soon. Apple Silicon. Public signed build is not available yet.
Verified releases only
Download Free. Launch Without the Subscription.
Download the verified Vibe Launch Master release for your desktop platform. A platform button appears only when a signed artifact is available; unreleased or paused platforms are shown honestly as Coming soon or Paused.
Target desktop platforms
A platform remains visible without pretending that an unreleased build is downloadable.
The current status is generated from the shared release facts. A real button requires an available signed artifact and official URL.
macOS
Coming soon. Intel. Public signed build is not available yet.
Windows
Coming soon. x64. Public signed build is not available yet.
Linux
Coming soon. x64. Linux is a product target. A verified public artifact is not available yet.
Release verification
Artifact, signature, version, checksum, and tested requirements must agree.
The website does not infer a download from roadmap support or a development build. Every public release fact must come from the official manifest.
Release evidence
Evidence required before a download becomes available.
Public state
What the public page may show after verification.
Field Release evidence Public state
Artifact Official file from the Vibe Launch Master release repository and manifest. The platform download button may appear.
Signature Signed, notarized, or otherwise verified for the platform where applicable. The signed state is shown next to the artifact.
Version Named version, published date, architecture, file size, and release notes. The Download and Changelog pages share the same release facts.
Checksum Published SHA-256 value for the exact file. The user can compare the downloaded file before installation.
Requirements Tested operating-system, disk, browser-bridge, and architecture requirements. Minimum requirements are published only after real artifact testing.
Platform status
A button appears only when the build is real.
The current development preview has no verified public desktop artifact. Every target platform remains visible so Coming soon is not confused with unsupported.
Coming soon
macOS
Apple Silicon
Public signed build is not available yet.
Coming soon
macOS
Intel
Public signed build is not available yet.
Coming soon
Windows
x64
Public signed build is not available yet.
Coming soon
Linux
x64
Linux is a product target. A verified public artifact is not available yet.
Release access
Public builds are not available yet.
The release-list endpoint is not connected in this development preview. No email is collected by this page.
System requirements
Verified minimum operating-system versions, required disk space, browser-bridge versions, and architecture requirements will appear with each signed release. No minimum requirement is published until it has been tested against the actual artifact.
How to verify the download
Every available build will show its version, signed state, published date, file size, and SHA-256 checksum. The website will only link to artifacts from the official Vibe Launch Master release repository and release manifest.
- Confirm the platform and architecture.
- Confirm the release is signed or notarized where applicable.
- Compare the SHA-256 checksum before installation.
- Review the matching release notes and known limitations.
What happens on first launch?
The desktop app begins with supported OAuth sign-in, product-source import, missing-material review, Launch Master confirmation, launch inbox connection, dedicated Chrome setup, AI connection, a short launch plan, and the first campaign.
Why does the app use a dedicated Chrome profile?
A dedicated profile keeps directory sessions, saved passwords, and launch activity separate from daily browsing. It also gives the user a real browser window for CAPTCHA, 2FA, Passkeys, identity verification, or any step that requires human attention.
Release notes and checksums
When a public artifact exists, the Download page and Changelog will share the same release facts. A changed platform state, version, checksum, provider capability, or known limitation must update both surfaces together.