Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
browser - Skill - OpenSmartRoute
Skillv1.0.0
browser
Web browser automation with AI-optimized snapshots for claude-flow agents
Imported from proffesor-for-testing/agentic-qe (.claude/skills/browser/SKILL.md). Install upstream with npx skills add proffesor-for-testing/agentic-qe --skill browser. Copyright stays with the author.
Browser Automation Skill
Web browser automation using agent-browser with AI-optimized snapshots. Reduces context by 93% using element refs (@e1, @e2) instead of full DOM.
Core Workflow
# 1. Navigate to pageagent-browser open <url># 2. Get accessibility tree with element refsagent-browser snapshot -i # -i = interactive elements only# 3. Interact using refs from snapshotagent-browser click @e2agent-browser fill @e3 "text"# 4. Re-snapshot after page changesagent-browser snapshot -i
Quick Reference
Navigation
Command
Description
open <url>
Navigate to URL
back
Go back
forward
Go forward
reload
Reload page
close
Close browser
Snapshots (AI-Optimized)
Command
Description
snapshot
Full accessibility tree
snapshot -i
Interactive elements only (buttons, links, inputs)
snapshot -c
Compact (remove empty elements)
snapshot -d 3
Limit depth to 3 levels
screenshot [path]
Capture screenshot (base64 if no path)
Interaction
Command
Description
click <sel>
Click element
fill <sel> <text>
Clear and fill input
type <sel> <text>
Type with key events
press <key>
Press key (Enter, Tab, etc.)
hover <sel>
Hover element
select <sel> <val>
Select dropdown option
check/uncheck <sel>
Toggle checkbox
scroll <dir> [px]
Scroll page
Get Info
Command
Description
get text <sel>
Get text content
get html <sel>
Get innerHTML
get value <sel>
Get input value
get attr <sel> <attr>
Get attribute
get title
Get page title
get url
Get current URL
Wait
Command
Description
wait <selector>
Wait for element
wait <ms>
Wait milliseconds
wait --text "text"
Wait for text
wait --url "pattern"
Wait for URL
wait --load networkidle
Wait for load state
Sessions
Command
Description
--session <name>
Use isolated session
session list
List active sessions
Selectors
Element Refs (Recommended)
# Get refs from snapshotagent-browser snapshot -i# Output: button "Submit" [ref=e2]# Use ref to interactagent-browser click @e2
CSS Selectors
agent-browser click "#submit"agent-browser fill ".email-input" "test@test.com"
Semantic Locators
agent-browser find role button click --name "Submit"agent-browser find label "Email" fill "test@test.com"agent-browser find testid "login-btn" click
Examples
Login Flow
agent-browser open https://example.com/loginagent-browser snapshot -iagent-browser fill @e2 "user@example.com"agent-browser fill @e3 "password123"agent-browser click @e4agent-browser wait --url "**/dashboard"
Form Submission
agent-browser open https://example.com/contactagent-browser snapshot -iagent-browser fill @e1 "John Doe"agent-browser fill @e2 "john@example.com"agent-browser fill @e3 "Hello, this is my message"agent-browser click @e4agent-browser wait --text "Thank you"
Data Extraction
agent-browser open https://example.com/productsagent-browser snapshot -i# Iterate through product refsagent-browser get text @e1 # Product nameagent-browser get text @e2 # Priceagent-browser get attr @e3 href # Link
Multi-Session (Swarm)
# Session 1: Navigatoragent-browser --session nav open https://example.comagent-browser --session nav state save auth.json# Session 2: Scraper (uses same auth)agent-browser --session scrape state load auth.jsonagent-browser --session scrape open https://example.com/dataagent-browser --session scrape snapshot -i
Integration with Claude Flow
MCP Tools
All browser operations are available as MCP tools with browser/ prefix:
browser/open
browser/snapshot
browser/click
browser/fill
browser/screenshot
etc.
Memory Integration
# Store successful patternsnpx ruflo@3.76.0 memory store --namespace browser-patterns --key "login-flow" --value "snapshot->fill->click->wait"# Retrieve before similar tasknpx ruflo@3.76.0 memory search --query "login automation"
Always use snapshots - They're optimized for AI with refs
Prefer -i flag - Gets only interactive elements, smaller output
Use refs, not selectors - More reliable, deterministic
Re-snapshot after navigation - Page state changes
Use sessions for parallel work - Each session is isolated
Installed into a catalogue, chosen by a router
Install browser and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
When a provider is down or over quota the request moves on; the trace says it did.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.