web-auth

Authenticate to websites via headed browser handoff with session persistence.

951|110|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/agent-sh/agentsys --skill web-auth-agent-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-auth
Source: https://github.com/agent-sh/agentsys/tree/main/.kiro/skills/web-auth
Command: npx skills add https://github.com/agent-sh/agentsys --skill web-auth-agent-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authenticate to websites with human-in-the-loop browser handoff. Use when user needs to log into a website, complete 2FA, or solve CAPTCHAs for agent access.

Core Features & Use Cases

  • Human-in-the-loop authentication: Open a browser window for the user to complete login steps.
  • Session persistence: Persist authenticated sessions for reuse across agent tasks.
  • Error handling: Manage timeouts, CAPTCHA detections, and provider-based flows with clear results.

Quick Start

Start a session and let the user complete login in a headed browser to obtain an authenticated session.

Frequently Asked Questions about web-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate an agent to a website that requires 2FA or CAPTCHA?

Web authentication uses a human-in-the-loop browser handoff to open a headed browser, letting you manually complete 2FA prompts or CAPTCHAs while the agent monitors for a successful login session.

Can I persist a browser session for reuse across multiple agent tasks?

Yes, web authentication uses a defined session lifecycle to persist the authenticated browser state, allowing you to reuse the active session across subsequent agent tasks without repeated manual logins.

How does human-in-the-loop browser handoff work for web login?

Human-in-the-loop browser handoff works by opening a visible browser window for you to complete the login steps, while the agent monitors the session state to detect successful authentication or handle timeouts.

Do I need a specific environment to handle CAPTCHA and 2FA authentication?

Yes, web authentication requires a browser-capable environment to open a headed browser window, which is necessary for you to interact with and solve CAPTCHA detections or complete 2FA flows manually.

What happens if a web authentication session times out or encounters a CAPTCHA?

Web authentication provides error handling for timeouts, CAPTCHA detections, and provider-based flows, returning clear results so you can manage failures and retry the login process if needed.

When should I use a human-in-the-loop approach for web authentication?

You should use human-in-the-loop web authentication when an agent needs to access a website with login flows, 2FA, or CAPTCHAs that cannot be automated and require manual user interaction to complete.