Email and OTPs for the Browser
Your Agent Already Runs
Keep your browser stack, whether that is Skyvern, Browserbase with Stagehand, Steel or your own Playwright, and give each run a real Lumbox inbox. The OTP or magic link comes back as JSON from one long-poll call. When a customer's login codes go to their own address, the customer forwards them to the inbox and the same call returns the code.
Bring your own browser
Each guide creates an inbox, uses its address in a signup, and reads the code from /otp. Customer forwarding works for email today. SMS forwarding from an iOS Shortcut or an Android forwarder is in early access and lands in the same inbox.
Or let Lumbox run the browser
Lumbox can also run a stealth browser session with the inbox and an encrypted credential vault attached, so the agent signs up and logs in without seeing the saved password. browser_act turns one planning call into a step plan that runs with no further LLM calls.
Stealth Chromium, Per Agent
A patched Chromium build with anti-bot fingerprint protection runs in isolated sessions. CAPTCHA solving is on by default. Save cookies and localStorage to disk so the browser is already logged in next time.
Credential Vault
Passwords, API keys, and TOTP secrets stored with AES-256-GCM envelope encryption. The vault types them straight into the browser form and blurs the field from vision models. The agent's conversation never contains the plaintext.
Skills That Compound
signup_with_email fills a registration form and harvests the OTP in one call. login_with_email runs the magic-link round trip. verify_email clicks the link in-browser. Six steps collapse into one.