WZRD Studio ships as an unsigned APFS DMG targeting macOS Apple Silicon. The steps below walk you through installing the pre-built DMG, bypassing Gatekeeper on first launch, configuring your environment, and optionally running the app from source for development.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/gratitude5dee/wzrd-studio-desktopfinal/llms.txt
Use this file to discover all available pages before exploring further.
Requirements
Before you begin, confirm your machine meets the following requirements:| Requirement | Minimum |
|---|---|
| macOS architecture | Apple Silicon (arm64) |
| Runtime | Bun (latest) |
| Node.js | Compatible with the project toolchain (see package.json) |
| Supabase project | Active project with ANON_KEY and URL available |
| Thirdweb project | Client ID from thirdweb.com/dashboard |
DMG Installation
Download the DMG
Obtain
wzrdstudiofinal555-apfs.dmg — either from the releases page or by building it yourself.Mount the DMG
Double-click
wzrdstudiofinal555-apfs.dmg. A Finder window opens showing the WZRD Studio.app bundle alongside an Applications shortcut.Bypass Gatekeeper on first launch
Because the DMG is unsigned and unnotarized, macOS will block the first launch with a security warning. Use one of the following methods to open the app:Option A — Right-click to open:
- Navigate to Applications.
- Right-click (or Control-click) WZRD Studio.app.
- Select Open from the context menu.
- Click Open in the confirmation dialog.
- Attempt to open WZRD Studio normally. macOS will block it.
- Go to System Settings → Privacy & Security.
- Scroll to the security section and click Open Anyway next to the WZRD Studio entry.
- Authenticate with Touch ID or your password when prompted.
You only need to bypass Gatekeeper once. Subsequent launches open normally. Auth deep-link redirects (
wzrd://auth/thirdweb) may also be blocked on the very first launch — repeating the right-click → Open step resolves this.Environment Setup
WZRD Studio reads configuration from a.env file at the project root. Create this file before launching the app in development mode or building from source.
Additional provider keys (e.g. for GMI Cloud, fal.ai, or Postz OAuth channels) may be required depending on which generation workflows you enable. Refer to the individual feature docs for the full list of keys each feature requires.
| Variable | Description |
|---|---|
VITE_SUPABASE_URL | Your Supabase project URL, found in Project Settings → API. |
VITE_SUPABASE_ANON_KEY | The public anon key for your Supabase project. |
VITE_THIRDWEB_CLIENT_ID | Your Thirdweb client ID, used for wallet authentication. |
Development Setup
To run WZRD Studio directly from source without packaging a DMG:Create the .env file
Follow the Environment Setup section above.
Start the web renderer only
Build the DMG from Source
To produce a fresh signed-APFS DMG:- Runs
vite buildto compile the renderer. - Calls
electron-builder --mac dir --arm64to package the Electron app. - Runs
scripts/build-apfs-dmg.mjsto assemble the APFS DMG (usinghdiutildirectly, avoiding HFS+ compatibility issues).
Verification
After installation or a new build, run the following checks to confirm everything is working:bun run desktop:test) builds the renderer and runs Playwright against the packaged Electron app using the playwright.electron.config.ts configuration.