Guide · Selenium

Selenium + Multilogin X

Legacy desks still shipping Selenium: start the profile with automation_type=selenium, then attach webdriver.Remote to http://127.0.0.1:{port}. New projects should prefer Playwright + CDP.

Plan gate: Free has no API — Pro+. Official Multilogin samples and the Postman Launcher folder remain the source of truth if paths move.

Mode A vs Mode B

• Mode A: Start via UI/Postman, put the returned WebDriver URL/port into env, connect only.
• Mode B: MD5 sign-in + Launcher start (automation_type=selenium) in the monorepo kit, then Remote attach. Agent must be running.

Launcher start

GET https://launcher.mlx.yt:45001/api/v2/profile/f/{folder_id}/p/{profile_id}/start
  ?automation_type=selenium&headless_mode=false
Authorization: Bearer {token}
→ data.port

Minimal Remote snippet (Python-shaped)

from selenium import webdriver
from selenium.webdriver.chrome.options import Options

options = Options()
driver = webdriver.Remote(
    command_executor=f"http://127.0.0.1:{port_from_launcher}",
    options=options,
)
driver.get("https://example.com")

Exact capability names can vary by Multilogin agent build — check their Selenium example before fighting DesiredCapabilities archaeology.

When attach fails

• App not running on this machine
• Wrong automation_type (selenium vs playwright)
• Expired token → token desk
• Port races / stale session → same class of failures as CDP attach

Kit location

No new public Selenium repo (hard lock). Starter lives in the monorepo: aff-saas/kits/selenium-mlx-starter/ on GitHub under aff-saas/kits.

Get codes on Telegram Prefer Playwright API map