Nearly every useful site is behind a login, and nearly every login now has a second factor, which is where hand-rolled automation dies. Integrating with password managers rather than asking you to paste credentials into a config is the right call, and it means the secrets stay where your organisation already manages them. Weigh the other side honestly: a connection that can log in as you, click anything and read the network is the most powerful thing in this catalogue and deserves a deliberate decision, not a casual one.
Skyvern drives a real browser. The endpoint is large because browser work is: sessions, every interaction, extraction, and the credential handling that logging in actually requires.
- Sessions, and browser actions — navigate, click, type, scroll
- Structured extraction, screenshots and JavaScript execution
- Credentials and login — a vault plus Bitwarden, 1Password and Azure Key Vault, with two-factor handled automatically
- Workflow orchestration across many block types
- The awkward parts: tabs, iframes, drag and drop, uploads, clipboard and network inspection
OAuth if your client supports it — Claude Code, Codex, Cursor and ChatGPT are named — or an API key header. It can also be self-hosted locally over stdio.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen