MultiBox — many copies of one program
MultiBox runs several copies of the same program side by side without them tripping over each other. Normally a second copy of a game or client simply refuses to open: the program notices it is already running and quits. MultiBox removes that obstacle and gives every copy its own settings, its own data folder and, if you want, its own separate route to the internet.
Launch and watch every copy
The Run Box lists every copy with its name, program and current state. When one fails to start, the AI Agent reads what actually happened and points at the real cause instead of a generic error.
- Add and remove copies
- Start all · Stop all
- AI reads the launch log and suggests a fix
The easiest way to picture it: each copy believes it is alone on the computer. It cannot see its neighbours, it does not fight them over settings files, and it can be signed into its own account. All of this is on the PRO tier.
What people use it for
- Play or farm on several accounts at once from one computer.
- Keep different accounts fully apart — each with its own saved logins.
- Give each account its own internet route so they do not look like one and the same source.
- Work out why a program refuses to start or crashes — MultiBox shows what happens inside.
- Run one scenario across several copies at once.
Run Box — the list of your copies
- Each copy is saved separately: its own name, program, working folder and settings.
- Start and stop buttons — for one copy or for all of them at once.
- Live state is visible: whether a copy is running, which processes it spawned, its system number.
- An event timeline shows what happened during startup, plus network activity.
- When a copy fails to start, the AI Agent reads the startup records and names the real cause.
Options — how a copy behaves
- Observe — the program starts as usual and MultiBox only watches and records. Start here.
- Assist — MultiBox gently helps two copies coexist: it separates their internal markers and hides their windows and processes from each other.
- Custom — full control: a separate Windows settings area per copy, hiding neighbours, and blocking a copy from shutting itself down.
- Its own application data folder per copy, so saves and settings never mix.
- Limits on processor, memory and number of processes, so a dozen copies cannot bring the machine down.
- Limits are applied before the program can do anything; if a required rule fails, the copy does not start at all.
Tunnel — a separate internet route per copy
- Each copy reaches the internet either directly or through its own proxy — copies never share an address or an account.
- SOCKS5 proxies are supported: address and port are set per copy. Username/password authentication is not supported yet — for such a proxy, use a local client on 127.0.0.1.
- All of the copy's traffic goes through the tunnel: TCP, UDP, DNS, IPv4 and IPv6 — the AIWeavio NetTool system service provides this.
- A test button tells you whether the proxy answers and shows the external IP address, before you even start the copy.
- Routing rules: send particular sites through the proxy and everything else direct, or the other way round.
- A rule can match a site address, an address ending (all its subdomains at once), a single IP address, or a whole address range.
- Site-name lookups are configured separately — automatic, through the proxy, or direct. This matters, because name lookups must not escape the tunnel.
- Strict mode: if the proxy is unreachable the copy simply does not start, instead of quietly falling back to a direct connection and exposing the real address. If the link drops mid-run, the copy's processes are closed.
- Routing profiles are saved and reused across copies, and speed, connections and errors are visible live. Full details are in Network & proxies.
One caveat about networking: the tunnel needs the AIWeavio NetTool system service. Its status is shown right on the Tunnel tab; if the service is stopped or damaged, repair it in Components — until then, SOCKS5 copies will not start.
Inspector — what is going on inside a copy
- Attaches after launch, to a chosen process of the copy.
- Shows the program's building blocks, its threads and the contents of its memory.
- Records which system functions the program calls and which events it raises.
- Lets you halt the program at a chosen point and inspect its state.
- Any change is previewed first, then needs your consent, and is verified afterwards — if it did not help, it is rolled back.
- The diagnostic report can be exported as a single file.
- Everything gathered is available to the AI Agent, which separates fact, guess and unknown instead of passing correlation off as cause.
An honest boundary: MultiBox separates copies at the level of ordinary user programs. It is not a virtual machine, not Windows Sandbox and not a security boundary. Hardened programs, drivers and kernel-level protection lie outside its reach, and behaviour with them is not guaranteed. If you need a genuinely separate Windows per copy, see the Sandbox section.