MultiBox opens every copy of an app in its own session folder, so each copy keeps separate logins, cookies and settings. Save the copies you want to keep. Wipe the rest with one click.
Guide
Five steps, about two minutes. The button names below match what you see in the app.
Download the latest MultiBox-v…-win-x64.zip from Releases, extract it to any folder and run MultiBox.exe. Nothing is installed.
Windows may show a SmartScreen warning the first time. Click More info → Run anyway. Why?
Drag an app's .exe or desktop shortcut onto MultiBox, or click Browse. It opens in a fresh, empty profile, the same as on a brand-new PC.
Optional: turn on Settings → Right-click launch to get Run in Isolated Mode (MultiBox) in File Explorer.
Click Another copy. Each copy is a separate session you can sign in to with a different account. Switch between sessions at the top, and use Name & color to label them (for example Chrome · Work).
Click Save and give it a name. MultiBox closes the app for a moment, copies its data safely, then reopens it. Find saved profiles under Vault → Saved and click Open to use one again.
Click Wipe to close a session and delete its temporary files. Saved profiles are kept. Closing MultiBox sends it to the system tray; right-click the tray icon to quit.
Features
MultiBox runs your apps normally, with no virtual machine. It points each copy at its own data folders and keeps track of every process that copy starts.
Every copy gets its own folder for app data, caches, cookies, temp files and local databases, separate from your Windows profile and from other copies.
Keep a session as a named profile, such as Work Slack or Client A, and open it again later in a fresh session.
See memory and CPU use for each session. The Tasks list also shows programs already open on your PC.
Screenshots
A 30-second tour: Cline opened three times, each copy with its own login, then saved for later. Click a screenshot below to enlarge it.
Compatibility
Most desktop apps keep their data in the folders MultiBox redirects. Each copy also gets its own Node.js / Bun home and temp folders, and its own background-service ports for apps that need them.
| App type | Examples | Status |
|---|---|---|
| Electron | Discord, Slack, VS Code, OpenCode | ✅ Own profile per copy |
| Chromium browsers | Chrome, Edge, Brave | ✅ Own --user-data-dir per copy |
| Tauri | Cline | ✅ Single-instance lock released, so a real second copy opens |
| WebView2 apps | Apps that use Edge WebView2 | ✅ Own WebView2 data per copy |
| Node.js & Bun | Bundled CLIs and background services | ✅ Home, temp and XDG folders per copy; OpenCode and Cline get their own service ports |
| Firefox & Thunderbird | Mozilla apps | ✅ Own -profile, -no-remote |
| Classic Win32 apps | 32-bit and 64-bit | ⚠️ Works if the app stores data in AppData; registry settings are shared |
| Microsoft Store desktop apps | Codex (ChatGPT), Claude | ✅ Start from their WindowsApps folder like any other app |
MultiBox separates app profiles. It is not a security sandbox: apps run with your normal permissions and can still read your files. Shared between copies:
HKEY_CURRENT_USER)AppData\LocalLow and the Windows "Profile" folder (Electron app.getPath('home'), Rust dirs::home_dir)Help
MultiBox is signed with a self-signed certificate (CN=zer0ne). Windows doesn't recognize self-signed publishers, so the first run shows a warning. Click More info → Run anyway. You can review the source code and build MultiBox yourself instead.
Some apps allow only one running copy and pass new launches to the open window. MultiBox handles the common methods: the Electron and Chromium profile lock, and Tauri's single-instance lock. If an app still does this, please open an issue with the app's name and version.
OpenCode Desktop starts a background service on a fixed port, so a second copy collided with the first. MultiBox 1.0.4 and later give every copy its own service port automatically. Update to the latest release.
Yes, briefly. To make a consistent copy, Save asks the app to close, copies its data, then reopens it in the same session. If the app has unsaved work or an open dialog, Save waits and nothing is lost.
Sessions live in %LOCALAPPDATA%\MultiBox\Vaults and saved profiles in %LOCALAPPDATA%\MultiBox\Vaults\SaveBox. The Vault panel has buttons that open both folders.
No. MultiBox runs as your normal user and installs no drivers or services.
No. Use a virtual machine or Windows Sandbox for that. MultiBox keeps app profiles apart; it does not restrict what a program can access.
For developers
Each session's app starts suspended inside a Windows Job Object, so every child process belongs to that session and closes with it.
USERPROFILE, APPDATA, LOCALAPPDATA, TEMP and the XDG folders point into the session's Vault, plus profile flags for Chromium, Electron and Firefox.
SaveBox copies SQLite databases with the online backup API and skips caches and lock files, which apps rebuild on their own.
MultiBox is designed and maintained by zer0ne. Bug reports and pull requests are welcome on GitHub.