Browser Automation with agent-browser

웹 브라우저를 자동화하여 테스트, 폼 작성, 스크린샷, 데이터 추출 등을 수행합니다.

Instructions

워크플로우: 탐색 → 분석 → 상호작용 → 검증

Quick start

agent-browser open <url> # Navigate to page agent-browser snapshot -i # Get interactive elements with refs agent-browser click @e1 # Click element by ref agent-browser fill @e2 "text" # Fill input by ref agent-browser close # Close browser

Core workflow

• Navigate: agent-browser open <url>

• Snapshot: agent-browser snapshot -i (returns elements with refs like @e1 , @e2 )

• Interact using refs from the snapshot

• Re-snapshot after navigation or significant DOM changes

Commands

Navigation

agent-browser open <url> # Navigate to URL agent-browser back # Go back agent-browser forward # Go forward agent-browser reload # Reload page agent-browser close # Close browser

Snapshot (page analysis)

agent-browser snapshot # Full accessibility tree agent-browser snapshot -i # Interactive elements only (recommended) agent-browser snapshot -c # Compact output agent-browser snapshot -d 3 # Limit depth to 3

Interactions (use @refs from snapshot)

agent-browser click @e1 # Click agent-browser dblclick @e1 # Double-click agent-browser fill @e2 "text" # Clear and type agent-browser type @e2 "text" # Type without clearing agent-browser press Enter # Press key agent-browser press Control+a # Key combination agent-browser hover @e1 # Hover agent-browser check @e1 # Check checkbox agent-browser uncheck @e1 # Uncheck checkbox agent-browser select @e1 "value" # Select dropdown agent-browser scroll down 500 # Scroll page agent-browser scrollintoview @e1 # Scroll element into view

Get information

agent-browser get text @e1 # Get element text agent-browser get value @e1 # Get input value agent-browser get title # Get page title agent-browser get url # Get current URL

Screenshots

agent-browser screenshot # Screenshot to stdout agent-browser screenshot path.png # Save to file agent-browser screenshot --full # Full page

Wait

agent-browser wait @e1 # Wait for element agent-browser wait 2000 # Wait milliseconds agent-browser wait --text "Success" # Wait for text agent-browser wait --load networkidle # Wait for network idle

Semantic locators (alternative to refs)

agent-browser find role button click --name "Submit" agent-browser find text "Sign In" click agent-browser find label "Email" fill "user@test.com"

Examples

Example 1: Form submission

agent-browser open https://example.com/form agent-browser snapshot -i

Output shows: textbox "Email" [ref=e1], textbox "Password" [ref=e2], button "Submit" [ref=e3]

agent-browser fill @e1 "user@example.com" agent-browser fill @e2 "password123" agent-browser click @e3 agent-browser wait --load networkidle agent-browser snapshot -i # Check result

Example 2: Authentication with saved state

Login once

agent-browser open https://app.example.com/login agent-browser snapshot -i agent-browser fill @e1 "username" agent-browser fill @e2 "password" agent-browser click @e3 agent-browser wait --url "**/dashboard" agent-browser state save auth.json

Later sessions: load saved state

agent-browser state load auth.json agent-browser open https://app.example.com/dashboard

Example 3: Data extraction

agent-browser open https://example.com/products agent-browser snapshot -i

Find product titles and prices

agent-browser get text @e5 # Product title agent-browser get text @e6 # Price agent-browser screenshot products.png

Advanced Features

Sessions (parallel browsers)

agent-browser --session test1 open site-a.com agent-browser --session test2 open site-b.com agent-browser session list

JSON output (for parsing)

Add --json for machine-readable output:

agent-browser snapshot -i --json agent-browser get text @e1 --json

Debugging

agent-browser open example.com --headed # Show browser window agent-browser console # View console messages agent-browser errors # View page errors

Best Practices

• Always snapshot before interacting: Get fresh refs after navigation or DOM changes

• Use interactive snapshot (-i ): Reduces noise, focuses on actionable elements

• Wait appropriately: Use wait --load networkidle after actions that trigger navigation

• Save auth state: Reuse login sessions with state save/load

• Take screenshots for verification: Visual confirmation of expected state

• Use semantic locators for stable tests: find role/text/label is more resilient than refs

Technical Details

• Based on Playwright browser automation

• Supports Chromium, Firefox, and WebKit

• Uses accessibility tree for element detection

• Provides stable references (@e1, @e2) for elements

• Handles common web testing scenarios out-of-the-box