MLX · Basic automation
How to Enable 2FA (Two-Factor Authentication) in CLI
Lock operator accounts with 2FA before you distribute API tokens across a team.
Why 2FA before automation
API tokens inherit the blast radius of the operator account that created them. Enabling 2FA reduces account-takeover risk when laptops, chat logs, or screenshots leak.
High-level CLI flow
Exact flags follow your installed Multilogin / MLX CLI version. Conceptually:
- Authenticate the CLI against your account.
- Start or open the 2FA enrollment command.
- Scan or enter the TOTP secret in your authenticator app.
- Confirm with a verification code.
- Store recovery codes offline (not in the repo).
- Re-auth CLI and confirm privileged commands still work.
# Illustrative — check `mlx --help` / vendor CLI docs for current verbs
mlx auth login
mlx account 2fa enable
mlx account 2fa verify --code 123456
Team policy
| Rule | Detail |
|---|---|
| Mandatory 2FA | All users who can create tokens |
| No shared authenticators | One human → one TOTP factor |
| Recovery codes | Sealed storage; rotate after use |
| Offboarding | Revoke tokens and remove 2FA device access paths |
After 2FA
Continue with the workspace ID and token setup runbook, then Postman automation setup or script runner.
Multilogin plans with partner discount: 50MAM / MAMOFF.