Action Recipes Reference

browsy detects structured action patterns on each page and emits them as SuggestedAction variants. Each action provides element IDs that an agent can use directly with click, type_text, check, and select operations.

Actions are detected after page type classification. Multiple actions can coexist on a single page (a login page might also have a Search action for the nav bar and a CookieConsent action for a banner).

SuggestedAction enum

#![allow(unused)]
fn main() {
#[derive(Debug, Clone, Serialize, Deserialize)]
#[serde(tag = "action")]
pub enum SuggestedAction {
    Login { ... },
    Register { ... },
    Contact { ... },
    FillForm { ... },
    Search { ... },
    EnterCode { ... },
    Download { ... },
    CaptchaChallenge { ... },
    CookieConsent { ... },
    Consent { ... },
    SelectFromList { ... },
    Paginate { ... },
}
}

All actions are serialized with a "action" tag field for easy pattern matching.

Login

Detected when the page has a visible password input, a nearby text/email input, and a submit button.

{
  "action": "Login",
  "username_id": 5,
  "password_id": 8,
  "submit_id": 12,
  "remember_me_id": 10
}

When it fires: Page has a visible password input and a nearby username/email input. Does NOT fire if the page also has registration context (confirm password + registration keywords) -- Register takes priority in that case. When a page has both login and registration sections (like Hacker News), Login takes priority over Register.

Usage: The MCP login tool and Python browser.login() use this action internally. They type into username_id and password_id, then click submit_id.

Register

Detected on registration pages: password field plus either a confirm password field or registration keywords in the title/heading.

{
  "action": "Register",
  "email_id": 3,
  "username_id": 4,
  "password_id": 7,
  "confirm_password_id": 9,
  "name_id": 2,
  "submit_id": 11
}

When it fires: Page has a visible password field AND either (a) two or more password fields (confirm password pattern) or (b) title/heading contains registration keywords (register, sign up, signup, create account, join, new account). Does not fire when login keywords are present alongside confirm password (dual login/register pages prefer Login).

Contact

Detected on contact forms: a textarea (message body) plus contact-related context in the title or headings.

{
  "action": "Contact",
  "name_id": 2,
  "email_id": 4,
  "message_id": 6,
  "submit_id": 8
}

When it fires: Page has a visible textarea AND title/heading contains contact keywords (contact us, contact form, get in touch, reach out, send us a message, inquiry).

FillForm

Generic form action for pages classified as Form that don't match a more specific pattern (Login, Register, Contact, Search).

{
  "action": "FillForm",
  "fields": [
    { "id": 3, "label": "First Name", "name": "first_name", "type": "text" },
    { "id": 5, "label": "Email Address", "name": "email", "type": "email" },
    { "id": 7, "label": "Phone", "name": "phone", "type": "tel" }
  ],
  "submit_id": 10
}

Each FormField contains:

When it fires: Page type is Form (2+ data-entry inputs) AND no more specific form action (Login, Register, Contact, Search) was already detected.

Search

Detected when a search input is present on the page.

{
  "action": "Search",
  "input_id": 15,
  "submit_id": 16
}

When it fires: Page has an input matching search criteria: type="search", role="searchbox", name="q", name contains "search", or placeholder contains "search". Prefers visible inputs but falls back to hidden ones (for JS-rendered search engines).

EnterCode

Detected on verification/2FA pages with code-related context.

{
  "action": "EnterCode",
  "input_id": 4,
  "submit_id": 6,
  "code_length": 6
}

When it fires: Title or heading contains verification keywords AND the page has a visible text/number/tel input. Does not fire if a password field is present (that is Login). Detects separate-digit inputs (width < 60px, 4-8 inputs) and reports the code length.

Usage: The MCP enter_code tool and Python browser.enter_code() use this action internally.

Download

Detected when the page has links or buttons with download-related text or file extension hrefs.

{
  "action": "Download",
  "items": [
    { "id": 20, "text": "Download v2.1.0", "href": "https://example.com/release.zip" },
    { "id": 22, "text": "Download PDF", "href": "https://example.com/guide.pdf" }
  ]
}

Each DownloadItem contains:

When it fires: Page has visible links or buttons where the text starts with "download" (and is short) or the href ends with a known file extension (.zip, .tar.gz, .dmg, .exe, .msi, .deb, .rpm, .pkg, .appimage, .pdf, .csv, .xlsx).

CaptchaChallenge

Detected when a CAPTCHA service is found in the HTML structure or the page is classified as Captcha.

{
  "action": "CaptchaChallenge",
  "captcha_type": "ReCaptcha",
  "sitekey": "6Le-wvkSAAAAABx7...",
  "submit_id": 15
}

When it fires: Page has a captcha field set (detected CAPTCHA service in HTML) OR page type is Captcha. See CAPTCHA Detection for details.

CookieConsent

Detected when the page has a cookie notice with accept/reject buttons.

{
  "action": "CookieConsent",
  "accept_id": 50,
  "reject_id": 52
}

When it fires: Page has a substantial text block (>30 chars) mentioning cookies/GDPR AND a button with accept-related text (accept all, accept cookies, allow cookies, allow all, agree, got it, i understand, i agree).

Consent

Detected on OAuth/authorization consent pages with approve/deny buttons.

{
  "action": "Consent",
  "approve_ids": [30],
  "deny_ids": [32]
}

When it fires: Title or heading contains OAuth keywords (authorize, allow access, grant permission, oauth, consent) AND the page has buttons with approve or deny text.

SelectFromList

Detected on pages with many links arranged in a list-like pattern.

{
  "action": "SelectFromList",
  "items": [10, 14, 18, 22, 26]
}

When it fires: Page has 5+ visible links that form 5+ distinct rows (links within 30px Y are grouped into the same row). The action provides the first link ID from each row as representative items.

Paginate

Detected when the page has next/previous navigation links or numbered page links.

{
  "action": "Paginate",
  "next_id": 100,
  "prev_id": 98
}

When it fires: Page has links with pagination text (next, prev, previous, >, >>, <, <<, and Unicode equivalents).

Detection order

Actions are detected in this order:

1. Register (or Login if no registration context)
2. EnterCode
3. Consent
4. Contact
5. Search
6. SelectFromList
7. CookieConsent
8. Paginate
9. FillForm (only if no more specific form action exists)
10. Download
11. CaptchaChallenge

Multiple actions can coexist. A login page with a cookie banner and nav search bar will have Login, CookieConsent, and Search actions simultaneously.