Repository navigation
ScriptZ Nightly
Pre-releaseNightly build of ScriptZ 0.11.1-nightly.202610070050 from 138f1a2 on main, built 2026-10-07 00:50 UTC.
Untested preview. Turn it on in ScriptZ under Settings → Updates → Get nightly builds, or download it directly:
- macOS (Apple Silicon): scriptz-nightly-macos-arm64.dmg
- Windows (x64): scriptz-nightly-windows-x64-setup.exe
Changes since the previous nightly
- ScriptZ 0.11.0 mit Agent-Modus, Ida-Aufträgen und neuem Look (3620627)
- Konto: Backend-URL aus dem Convex-Deploy an den Website-Build geben (ad3d53f)
- Konto: SITE_URL prüfen, Fallback-Build ohne Backend-URL (df06ffd)
- Website: Konto mit Anmeldung und Registrierung (Convex + Better Auth) (cf496b4)
- Website: erstes Vercel-Deployment nicht mehr überspringen (46cb25c)
Installation (first time only)
macOS (Apple Silicon)
-
Download the
.dmgbelow and open it. -
Drag ScriptZ.app into your Applications folder.
-
The app is not signed (no Apple Developer account), so macOS
refuses to launch it. Run this command in Terminal once to remove
the quarantine flag:xattr -cr "/Applications/ScriptZ.app" -
Open ScriptZ from the Applications folder - it now launches
normally.
Without step 3, you'll see the message "ScriptZ is damaged and can't
be opened" or "can't be opened because the developer cannot be
verified". That's macOS Gatekeeper, not the app.
Windows (x64)
- Download the
.exeinstaller below and run it. - On first launch, Windows SmartScreen kicks in: "Windows
protected your PC". The app is not signed (no EV code-signing
certificate), so SmartScreen doesn't know it yet. - Click "More info", then the button that appears: "Run
anyway". - From there on, ScriptZ runs normally. Auto-updates work without
any further friction.
Without step 3, SmartScreen aborts the launch. That's Windows
protection, not the app.