Control browser, automate browser interactions, navigate to URLs, click on webpages, fill forms, take screenshots, inspect webpages, web scraping with browser, test websites manually, or interact with web pages programmatically using ATR browser server mode. Pairs with the atr-computer skill when a workflow needs the OS desktop too (drag-and-drop from the file manager, system dialogs, native apps).
Control browser, automate browser interactions, navigate to URLs, click on webpages, fill forms, take screenshots, inspect webpages, web scraping with browser, test websites manually, or interact with web pages programmatically using ATR browser server mode. Pairs with the atr-computer skill when a workflow needs the OS desktop too (drag-and-drop from the file manager, system dialogs, native apps).
allowed-tools
Bash(atr browser:*)
Companion skill — atr-computer controls the OS desktop (mouse, keyboard, screen, windows, app launch, plus an in-process LLM agent via atr computer ask). Load both when:
The browser action needs an OS file picker, drag from the file manager, or anything outside the page (e.g. authentication via 1Password desktop app).
You want a single high-level instruction to span web + desktop — atr computer ask "<instruction>" can call atr browser along the way.
Browser daemon listens on port 9333; computer daemon on 9334. Both can run simultaneously.
ATR Browser Automation Skill
This skill provides browser automation capabilities through ATR's browser server mode. The browser server runs as a daemon process and accepts CLI commands for browser control.
Architecture
Claude Code --> atr CLI (client) --> ATR Server + Browser
The browser runs in visible (non-headless) mode by default for debugging and verification.
Getting Started
Step 1: Check Browser Status and Start if Needed
Before any browser operations, verify the browser server is running:
atr browser status
If the server is not running, start it:
atr browser start
The server stores state at ~/.atr/browser.state which allows subsequent commands to discover the endpoint automatically.
Step 2: Navigate and Interact
Once running, use navigation and interaction commands to control the browser.
Screenshot Note: Use --file to save screenshots to /tmp/ with a timestamped filename (e.g., /tmp/atr-screenshot-20240105-103045.png). Add --full for full-page screenshots. Use --selector / -s to screenshot a specific element by CSS selector (e.g., -s "header", -s "#nav", -s "main > section:nth-child(2)"). Combine --selector with --full to capture an element's full scrollable height. Use --selector-all to screenshot every matching element as numbered PNGs — elements that fail or timeout are skipped (use --timeout <ms> to control per-element timeout, default 30s). Without --file, returns base64-encoded image data.
Debugging Commands
Command
Description
atr browser console [--limit N]
Get console messages (default: 50)
atr browser network [--limit N]
Get network requests (default: 50)
atr browser errors
Get failed requests
Workflow Pattern
Follow this workflow for browser automation tasks:
Ensure Server Running
atr browser status || atr browser start
Navigate to Target
atr browser navigate https://example.com
Inspect Page Elements
atr browser snapshot
This returns elements with unique IDs (UIDs) like e0, e1, etc.
Interact with Elements
Target elements by:
Text content: "Sign In"
UID from snapshot: e5
CSS selector: .submit-button
Verify Results
atr browser url
atr browser title
atr browser screenshot --file
Cleanup When Done
atr browser stop
Asking Questions About a Page
Use atr browser ask when you need specific information from a page without flooding your context with raw HTML or snapshot data. A lightweight sub-agent inspects the page using multiple tools and returns a concise text answer.
atr browser ask "What is the main heading on this page?"
atr browser ask "How many items are in the navigation menu?"
atr browser ask "Is there a login form on this page?"
Prefer ask over html or snapshot when:
You need a specific fact, not the full page structure
You want to keep your context clean for subsequent reasoning
The answer can be expressed as a short text response
Recording Browser Interactions
Use atr browser record to capture user interactions and output a .test.txt behavior test file. A floating overlay appears in the browser showing recorded steps in real time.
# Record interactions on a page
atr browser record --url https://example.com -o repro-steps.test.txt
# Record on the already-open page
atr browser record -o flow.test.txt
Stop recording with Ctrl+C in the terminal or the "Stop" button in the browser overlay.
The recorder captures clicks, form fills, keyboard shortcuts, navigation, scrolling, and select changes. It handles shadow DOM (web components) and generates stable CSS selectors. Password fields are automatically masked.
The output .test.txt file can be replayed with atr run --behavior repro-steps.test.txt.
Using JSON Output
Add --json flag for structured output when parsing is needed:
