Antidetect browser

The Antidetect Browser box (globe icon, column 2) connects the tool to the antidetect software that actually opens the browser profiles. The tool supports four platforms, each revealing a different set of fields. The antidetect app must be running for the tool to connect.

GAIO needs an antidetect browser — it does not open a browser of its own. The tool drives profiles inside GPMLogin, GPMLogin Global, Multilogin X or Hidemium, so one of those has to be installed and running before you press Start. Installing GAIO on its own is not enough. If you do not have one yet: register for GPMLogin.

Platform selector

The Platform dropdown at the top of the box offers four choices:

Platform	What it is	Default port
GPMLogin	Local GPMLogin app (older v3).	`19995`
GPMLogin Global	Newer v5 API gateway.	`9495`
Multilogin X	Cloud platform, sign in with email/password.	—
Hidemium	Local Hidemium V4 app, local API with no sign-in.	`2222`

Connecting Hidemium

Pick Hidemium and the only field you need is Port — the local API of the Hidemium V4 app, default 2222, no sign-in required. Start the Hidemium app, then press Test connection: the tool reports how many profiles it can see.

The Profile Name column on the Accounts tab accepts the profile NAME (the tool resolves the id for you) or the UUID itself — like GPMLogin, not id-only as with Multilogin.

Writing the proxy into a Hidemium profile requires a PAID Hidemium plan. The proxy API is only open to paid accounts; on the free plan the tool cannot write it and the profile keeps its previous proxy — in that case set the proxy inside the Hidemium app (Edit proxy) before running.

With Hidemium the tool also does bulk profile creation, detecting accounts with no profile and profile deletion — the same set as GPMLogin. Profiles the tool creates each get a different screen resolution, GPU and browser version.

When you switch between GPMLogin and GPMLogin Global, the tool auto-swaps the default port (19995 ↔ 9495) — but only if the port field still holds the other platform's default. Choosing Multilogin X forces Scale to 100, disables the Update proxy before run toggle, and shows a blue note that Multilogin doesn't support visual scale.

Connecting GPMLogin / GPMLogin Global

For the two GPMLogin platforms the field to fill is Port — the local API port the tool uses to talk to the GPMLogin app (open/close profiles, read the list).

Open the GPMLogin app — Make sure the antidetect software is running on the machine.
Pick the platform — Open the Platform dropdown and choose GPMLogin or GPMLogin Global.
Check the Port — For GPMLogin leave 19995. For GPMLogin Global, get the port from the app: Settings → API Gateway (default 9495).
Test it — Click Test Connection and read the result to the right of the button.
Save — Click Save Automation.

Connecting Multilogin X

Choosing Multilogin X reveals a block of fields to sign in and pick the folder that holds your profiles.

Pick the platform — Set Platform = Multilogin X.
Enter credentials — Fill your Multilogin Email and Password (password is masked).
Choose a folder — Paste a UUID into Folder ID, or click Fetch to load your folders, then pick one from the dropdown (it shows the name and profile count).
Test it — Click Test Connection, then Save Automation.

The Fetch button is disabled until both Email and Password are filled. With Multilogin, proxies must be set inside the Multilogin UI before running — the tool won't set them for you. And in the accounts DB, the Profile Name column must be the Multilogin profile UUID.

Test Connection

The Test Connection ghost button (at the bottom of the box) checks whether the tool can reach the selected platform using the values currently on screen — even if you haven't saved yet.

Result	Meaning
✓ GPMLogin OK (N profiles)	GPMLogin reached, N profiles visible.
✓ Multilogin signin OK	Multilogin sign-in succeeded.
✗ Connection failed	Wrong port or the antidetect app isn't running.
✗ Request failed	Network error.

The result message auto-clears after about 5 seconds. If you see ✗ Connection failed, the first things to check are: is the antidetect app open, and does the port match?