The launcher is a desktop application for Windows, macOS (Apple Silicon) and Linux.
It can install, update, reinstall and run Invoke Community Edition. It is self-contained, so you don't need to worry about having the right python version installed.
Click the link for your system to download the latest version of the launcher.
You can also download all releases, including prerelease versions, from this repo's GitHub releases.
You can install the latest stable release or latest prerelease versions of Invoke using the launcher.
The Launcher checks for updates once on startup and prompts you if one is available. It will update itself if you accept the update.
If installation fails, retrying the install in Repair Mode may fix it. There's a checkbox to enable this on the Review step of the install flow.
If that doesn't fix it, clearing the uv cache might do the trick:
uv cache clean.If you are still unable to install, try installing to a different location and see if that works.
If you still have problems, ask for help on the Invoke discord.
Like the install script, the launcher creates and manages a normal python virtual environment.
We suggest leaving the
venvalone and letting the launcher manage it, but you can interact with it like you would anyvenvif you need to.
Unlike the invoke script, the launcher provides a GUI to run the app.
The "old" scripts will be phased out over time. The goal is to support 3 ways to install and run Invoke:
venv manually, install the invokeai package, run it as a script)Yes, but we won't keep them updated for too much longer. Theoretically, they should continue to work for some time, even without updates.
The launcher is an electron application with React UI. We bundle uv with the build and then call it to install python, create the app venv, and run the app.
There are a number of lighter-weight systems that enable cross-platform builds. Tauri is probably the most popular, but there are others.
These other systems use the OS-provided engine to render their UIs. That means on Windows uses WebView2 (Chromium), macOS uses WebKit (Safari), and Linux uses WebKitGTK (basically a Linux port of Safari), and the version of the engine depends on the computer.
The result is an inconsistent user experience, and increased workload for devs to support the various rendering engines.
Electron uses the same version of Chrome for all platforms. We only need to build for one rendering engine target, and we can be far more confident in a consistent, bug-free application.
Electron uses about 10x more disk space than something like Tauri, but we're still only talking ~150MB max. You are going to install many GB of models, right? The extra disk usage is a drop in the bucket and both devs and users have a much better experience.
Contributions are welcome!
If you want to contribute something more than a simple bug fix, please first check in with us on discord. Ping @psychedelicious in the dev-chat or installer-chat forums.
This project uses node 22 and npm as its package manager.
npm i to install all packages. See the next section to get uv set up.npm run start to start the launcher in dev mode.npm run lint to run code quality checks.Building the launcher is very simple:
npm i: install dependenciesnpm run package: build for your system's platformAs described in the next section, you do need to manually download the uv binary to get a functioning build.
uv for local devThe uv binary is required to build the project locally or run the launcher in development mode.
To fetch the uv binary for your operating system, use the following script. Replace PLATFORM with one of the following options based on your system:
linux for Linuxwin for Windowsmac for macOSnpm run download PLATFORM
This will download the appropriate uv binary and place it in the assets/bin/ directory, which matches the file structure expected by the build process.
On macOS, you may need to remove the quarantine flag from the uv binary:
xattr -d 'com.apple.quarantine' assets/bin/uv
Local builds may require you to manually allow them to run on Windows and macOS.
Windows will prompt you to allow the app to run, but on macOS it may refuse, saying the app is damaged. Remove the quarantine flag from the .app package to resolve this:
xattr -d 'com.apple.quarantine' /Applications/Invoke\ Community\ Edition.app
Windows and macOS production builds built via the .github/workflows/build-and-sign.yml workflow are signed. Linux builds are never signed.
The launcher is a desktop application for Windows, macOS (Apple Silicon) and Linux.
It can install, update, reinstall and run Invoke Community Edition. It is self-contained, so you don't need to worry about having the right python version installed.
Click the link for your system to download the latest version of the launcher.
You can also download all releases, including prerelease versions, from this repo's GitHub releases.
You can install the latest stable release or latest prerelease versions of Invoke using the launcher.
The Launcher checks for updates once on startup and prompts you if one is available. It will update itself if you accept the update.
If installation fails, retrying the install in Repair Mode may fix it. There's a checkbox to enable this on the Review step of the install flow.
If that doesn't fix it, clearing the uv cache might do the trick:
uv cache clean.If you are still unable to install, try installing to a different location and see if that works.
If you still have problems, ask for help on the Invoke discord.
Like the install script, the launcher creates and manages a normal python virtual environment.
We suggest leaving the
venvalone and letting the launcher manage it, but you can interact with it like you would anyvenvif you need to.
Unlike the invoke script, the launcher provides a GUI to run the app.
The "old" scripts will be phased out over time. The goal is to support 3 ways to install and run Invoke:
venv manually, install the invokeai package, run it as a script)Yes, but we won't keep them updated for too much longer. Theoretically, they should continue to work for some time, even without updates.
The launcher is an electron application with React UI. We bundle uv with the build and then call it to install python, create the app venv, and run the app.
There are a number of lighter-weight systems that enable cross-platform builds. Tauri is probably the most popular, but there are others.
These other systems use the OS-provided engine to render their UIs. That means on Windows uses WebView2 (Chromium), macOS uses WebKit (Safari), and Linux uses WebKitGTK (basically a Linux port of Safari), and the version of the engine depends on the computer.
The result is an inconsistent user experience, and increased workload for devs to support the various rendering engines.
Electron uses the same version of Chrome for all platforms. We only need to build for one rendering engine target, and we can be far more confident in a consistent, bug-free application.
Electron uses about 10x more disk space than something like Tauri, but we're still only talking ~150MB max. You are going to install many GB of models, right? The extra disk usage is a drop in the bucket and both devs and users have a much better experience.
Contributions are welcome!
If you want to contribute something more than a simple bug fix, please first check in with us on discord. Ping @psychedelicious in the dev-chat or installer-chat forums.
This project uses node 22 and npm as its package manager.
npm i to install all packages. See the next section to get uv set up.npm run start to start the launcher in dev mode.npm run lint to run code quality checks.Building the launcher is very simple:
npm i: install dependenciesnpm run package: build for your system's platformAs described in the next section, you do need to manually download the uv binary to get a functioning build.
uv for local devThe uv binary is required to build the project locally or run the launcher in development mode.
To fetch the uv binary for your operating system, use the following script. Replace PLATFORM with one of the following options based on your system:
linux for Linuxwin for Windowsmac for macOSnpm run download PLATFORM
This will download the appropriate uv binary and place it in the assets/bin/ directory, which matches the file structure expected by the build process.
On macOS, you may need to remove the quarantine flag from the uv binary:
xattr -d 'com.apple.quarantine' assets/bin/uv
Local builds may require you to manually allow them to run on Windows and macOS.
Windows will prompt you to allow the app to run, but on macOS it may refuse, saying the app is damaged. Remove the quarantine flag from the .app package to resolve this:
xattr -d 'com.apple.quarantine' /Applications/Invoke\ Community\ Edition.app
Windows and macOS production builds built via the .github/workflows/build-and-sign.yml workflow are signed. Linux builds are never signed.