Skip to main content

Overview

Browser Hand is an AI-powered web automation agent that interacts with real websites on your behalf — navigating pages, clicking buttons, filling forms, and completing complex multi-step workflows with safety guardrails. Category: Productivity
Icon: 🌐

What It Does

1

Navigate Websites

Load any URL and read page content
2

Interact with Elements

Click buttons/links, fill form fields, select dropdowns
3

Extract Information

Read page content, take screenshots, capture data
4

Complete Multi-Step Tasks

Search products, compare prices, book appointments, submit forms
5

Safety Guardrails

ALWAYS ask for approval before purchases or payments

Requirements

Browser Hand requires Python 3 and Playwright browser automation library.

Python 3

Playwright

Estimated setup time: 3-5 minutes

Configuration

Browser Settings

Purchase Approval is ON by default and cannot be disabled for payments. Browser Hand will NEVER auto-complete purchases without your explicit confirmation.

Activation

Basic Setup

Configure settings:

Example Workflows

Browser Hand will:
  1. Navigate to amazon.com
  2. Find search box (input[type="search"])
  3. Type “mechanical keyboards under $100”
  4. Click search or submit
  5. Read results page
  6. Extract top 3 products with names, prices, ratings
  7. Present results as a table

Form Filling

Multi-Step Research

How It Works

1. Browser Session

Browser Hand maintains a persistent browser session across tool calls:
Session features:
  • Cookies persist across page navigations
  • Login state maintained
  • Session ends when conversation ends or when you close it explicitly

2. Core Browser Tools

browser_navigate

Navigate to a URL:
Waits for page to load (DOM ready).

browser_read_page

Read current page content:
Output example:

browser_click

Click an element by CSS selector or visible text:

browser_type

Type text into an input field:

browser_screenshot

Capture a screenshot:
Saves to current directory.

browser_close

Close the browser session:
Frees resources. Session auto-closes at conversation end.

3. Element Selection

CSS Selectors (preferred): Fallback to visible text: If CSS selector fails:

4. Common Patterns

Search Pattern

1

Navigate to site

browser_navigate({url: "https://example.com"})
2

Find search box

input[type="search"], input[name="q"], #search
3

Type query

browser_type({selector: "input[name='q']", text: "query"})
4

Submit

browser_click({selector: "button[type='submit']"}) or Enter auto-submits
5

Read results

browser_read_page()

Login Pattern

1

Navigate to login page

browser_navigate({url: "https://example.com/login"})
2

Fill email

browser_type({selector: "input[name='email']", text: "user@example.com"})
3

Fill password

browser_type({selector: "input[name='password']", text: "password123"})
4

Click login

browser_click({selector: "button[type='submit']"})
5

Verify success

browser_read_page() to check for dashboard/welcome message
NEVER store passwords in memory. Browser Hand asks for credentials when needed but does not save them.

E-commerce Pattern

1

Search product

Navigate and search
2

Click product

Click from results
3

Select options

Size, color, quantity
4

Add to cart

browser_click({text: "Add to Cart"})
5

Navigate to cart

browser_click({text: "Cart"})
6

Review items

browser_read_page() to see cart contents and total
7

STOP - Ask for approval

CRITICAL: Summarize cart and total, ask user for confirmation
8

Checkout (only if approved)

Proceed to checkout ONLY after user confirms

5. Purchase Approval (MANDATORY)

Before ANY purchase, payment, or order submission:
  1. Summarize what you are about to buy
  2. Show the total cost
  3. List all items in the cart
  4. STOP and ask the user for explicit confirmation
  5. Only proceed after receiving clear “yes” approval
Browser Hand NEVER auto-completes purchases. NEVER clicks “Place Order”, “Pay Now”, “Confirm Purchase”, or any payment button without user approval.
Example approval flow:

6. Error Recovery

Element not found:
Page doesn’t load:
CAPTCHA detected:

Output

Browser Hand generates:

Dashboard Metrics

  • Pages Visited — Total page navigations
  • Tasks Completed — Number of successful workflows
  • Screenshots — Screenshots captured

Use Cases

Product Research

Appointment Booking

Form Submission

Data Extraction

Monitoring

Tips & Best Practices

For best results:
  • Use headless=false for debugging (see what the browser is doing)
  • Take screenshots before critical actions for verification
  • Be specific with selectors — IDs and names are more reliable than classes
  • Test workflows manually first to understand page structure
  • Use max_pages_per_task to prevent infinite navigation loops

Common Issues

“Element not found”
Page structure may differ. Try visible text instead of CSS selector, or ask for a screenshot to debug.
“Page didn’t load”
Some sites are slow. Increase wait time or retry.
“Got CAPTCHA”
Browser Hand cannot solve CAPTCHAs. Use headless=false and solve manually.
“Login required”
Provide credentials when asked. Never store them in memory.
“Site blocked automation”
Some sites detect Playwright. This is a limitation of browser automation.

Security Rules

Security guidelines:
  • NEVER store passwords or credit card numbers
  • NEVER auto-complete payments without approval
  • NEVER navigate to URLs from untrusted sources without verification
  • NEVER fill credentials without user explicitly providing them
  • If you encounter phishing or suspicious content, warn the user immediately
  • Always verify you’re on the correct domain before entering sensitive info

Advanced Usage

Multi-Step Workflows

Conditional Logic

Scheduled Monitoring

Next Steps

Researcher Hand

Research websites for deeper analysis

Collector Hand

Monitor websites for changes