Network and proxies: three levels
AIWeavio has three independent network settings, each with its own job: a proxy for the app's own requests, a separate route for every MultiBox copy, and the network of Sandbox virtual machines. They can be combined any way you like.
Settings · Network
Proxy for API and AI Agent
Route API GET / POST nodes and AI Agent traffic through a dedicated HTTP / SOCKS proxy — with bypass list and a Test proxy button.
- HTTP / SOCKS
- System-proxy fallback
- Bypass list + test
App proxy
FreeFor web-request blocks and for the AI Agent. HTTP, HTTPS or SOCKS5, with login and a bypass list.
MultiBox copy tunnel
PROEach copy of a program gets its own SOCKS5 route, per-site rules and a leak-proof strict mode.
Sandbox network
PROThe whole virtual machine: no network, internet only, with the local network, or entirely through SOCKS5.
App proxy (Settings → Network)
- Covers the GET/POST request blocks and the AI Agent's calls to its provider. Does not affect games or MultiBox copies.
- Off — AIWeavio uses the Windows system proxy.
- On — pick the type (HTTP, HTTPS or SOCKS5), address and port, and optionally login, password and a list of bypassed addresses.
- Test proxy sends a short HTTPS request and shows right away whether the setup works.
MultiBox copy tunnel
- Each copy gets a route: direct, or through its own SOCKS5 proxy given as address:port.
- All of the copy's traffic goes through the tunnel: TCP, UDP, site-name lookups (DNS), IPv4 and IPv6. The AIWeavio NetTool system service provides this; if something is wrong with it, the app offers to repair it in Components.
- The Test button checks the route before launch and shows the external IP address the copy will use on the internet.
- Strict mode: without a working proxy the copy will not start, and if the link to the network helper drops mid-run, every process of the copy is closed — the real address does not leak.
- Network changes for a running copy apply on its next launch.
- Right now the tunnel connects to SOCKS5 without a username and password. If your proxy needs authentication, run a local proxy client on the computer and point the copy at its 127.0.0.1:port address.
Split routing
- A routing profile is a set of rules assigned to copies. One profile can be given to several copies at once. The built-in Full Tunnel profile sends everything through the proxy.
- A rule matches an exact domain, a domain with all its subdomains, an exact IP address, or a whole network (CIDR), for IPv4 and IPv6.
- Each rule sends traffic through SOCKS5 or direct. Rules are checked top to bottom; reorder them with Up and Down.
- If no rule matches, the profile's default route applies.
- For each rule you choose separately how site-name lookups travel: as the rule says, through SOCKS5, or direct.
- Domain rules need ordinary visible DNS. Encrypted DNS (DoH) and DNS over TCP follow the IP rules or the default route.
Live network activity
- Download and upload speed chart for the last 60 seconds of a running copy.
- Connection and error counts, and how many of the copy's processes the tunnel covers.
- How much traffic went through the proxy and how much went direct by the rules.
Sandbox network
- No network, internet only, internet and local network, or SOCKS5 for all of the machine's traffic.
- SOCKS5 mode supports a username and password; the password is stored encrypted for that machine only.
- For UDP to go through the proxy too, the server must support UDP ASSOCIATE. The mode is still in testing.
- Details are in the Sandbox section.