Desktop launcher

One download. Every tool in the suite, kept current.

Toolbox installs itself once, then updates itself and every tool inside it on every start. Nothing to redownload when a tool ships a new version, and nothing to install by hand when a new tool joins the suite.

Windows 10 or 11, 64-bit. Installer is about 2 MB. No admin prompt.

How it works

Three steps, and only the first one is yours

You run the installer. Everything after that happens on its own, every time the launcher opens.

1

Install once

Run the installer. It is a per-user install with no admin prompt, and it fetches WebView2 on its own if your machine needs it.

2

It updates itself

Before the window opens, the launcher checks for a newer version of itself, installs it if one exists, and restarts. What you see is always current.

3

Tools appear

Installed tools are brought up to the catalog version on the same start. A tool released today shows up in a launcher installed last month, no download required.

The suite

What is in it right now

Toolbox is the launcher. The tools inside it are what you actually use, and the catalog grows without a new launcher release.

WardrobeKit Creation

Build, preview and export clothing packs for GTA V. Import drawables and textures, preview them on a live ped, fix numbering, and export a resource ready to drop in.

Coming soon Installs through the launcher when it ships
More coming

Each new tool is a catalog entry, not a new download for you. It shows up in the library the day it ships.

No install needed yet
Auto-update model

Why the update sits inside the launcher

A suite of tools usually means a folder of installers that fall out of date the day you stop checking for them. Toolbox moves that job into the launcher itself, so it happens on a schedule you do not have to remember: every time you open it.

On start, the launcher checks its own update channel first. If a new build exists, it downloads, verifies the signature, installs and restarts before the window ever renders. Then it fetches the tool catalog and brings every installed tool up to the version listed there.

Shipping a tool update never means shipping a new launcher. The catalog is the only thing that changes, so a tool release can go out on its own schedule, and you get it on your next start.

Launcher checks itself first
Every start, before the library opens.
Installed tools follow
Brought to the catalog version in the same start.
Signed and checksummed
Launcher updates are signature verified. Tool packages are checksummed before they replace anything.