agent-browser
Automate websites with the agent-browser CLI for navigation, form flows, screenshots, extraction, and repeatable browser tasks. Use when users ask to interact with web apps, gather evidence from pages, or run browser-based QA steps.
- License 许可
- Apache-2.0
- 所属仓库
- getsentry/junior
- 最近更新
- 2026-11-12
- Stars
- ★ 413
- Forks
- 45
01 前言 Front Matter
- name
- agent-browser
- description
- Automate websites with the agent-browser CLI for navigation, form flows, screenshots, extraction, and repeatable browser tasks. Use when users ask to interact with web apps, gather evidence from pages, or run browser-based QA steps.
02 资源文件 10
- 参考文档references/authentication.md4.9 KB
- 参考文档references/commands.md9.6 KB
- 参考文档references/profiling.md3.3 KB
- 参考文档references/proxy-support.md4.9 KB
- 参考文档references/session-management.md4.2 KB
- 参考文档references/snapshot-refs.md4.2 KB
- 参考文档references/video-recording.md3.5 KB
- 脚本templates/authenticated-session.sh3.6 KB
- 脚本templates/capture-workflow.sh1.8 KB
- 脚本templates/form-automation.sh1.8 KB
03 SKILL.md 正文
Browser Automation
Use this skill when work requires real browser interaction instead of API-only lookups.
Core Workflow
- Open target page:
agent-browser open <url>
- Capture interactive refs:
agent-browser snapshot -i
- Interact by ref:
agent-browser click @e1agent-browser fill @e2 "value"
- Re-snapshot after every navigation or significant DOM change:
agent-browser snapshot -i
- Capture result evidence:
agent-browser screenshot --annotate <file.png>
Operational Rules
- Use
agent-browserdirectly; do not usenpx agent-browser. - Prefer one named session for multi-step flows:
agent-browser --session <name> ...
- Use chained commands with
&&only when no intermediate output is needed. - For commands that need refs (
@e*), runsnapshot -ifirst and use fresh refs. - If page load is async-heavy, wait explicitly:
agent-browser wait --load networkidle
- For user-facing findings, include screenshots and the exact page URL.
- When a user asks to see/share a screenshot in Slack, use
sendFileswith the screenshot path infilesso the image is included in the active conversation. - Never claim a screenshot was shared unless
sendFilesreturned success in this turn. - If
sendFilesis unavailable or file attachment fails, state the failure clearly and include the saved screenshot path or error instead of claiming success.
Common Patterns
Form flow
agent-browser --session demo open https://example.com/signup
agent-browser --session demo wait --load networkidle
agent-browser --session demo snapshot -i
agent-browser --session demo fill @e1 "user@example.com"
agent-browser --session demo click @e2
agent-browser --session demo wait --load networkidle
agent-browser --session demo screenshot --annotate /tmp/signup-result.png
Structured extraction
agent-browser open https://example.com
agent-browser snapshot --json > /tmp/page.json
agent-browser get text body > /tmp/page.txt
Reference Files
Read only what is needed:
- Command surface: references/commands.md
- Auth vault + login flows: references/authentication.md
- Session/state persistence: references/session-management.md
- Snapshot refs and stale-ref handling: references/snapshot-refs.md
- Proxy/network setup: references/proxy-support.md
- Recording and video capture: references/video-recording.md
- Performance profiling: references/profiling.md
Templates
- Authenticated flow bootstrap: templates/authenticated-session.sh
- Capture workflow skeleton: templates/capture-workflow.sh
- Form automation skeleton: templates/form-automation.sh
04 同仓库更多 Skills
junior
Build, review, or update Junior extension skills and plugins. Use when users ask to create a Junior SKILL.md, app skill, plugin, plugin.yaml, packaged plugin, MCP-backed plugin, OAuth or credentialed plugin, or to validate Junior extension files. Do not use for ordinary Junior usage, provider workflows, generic code editing, or non-Junior agent-skill authoring.
junior-qa
Validate Junior changes through local app-facing paths. Use for local client or agent QA, dashboard mock reporting UI QA, sharing a preview URL of a running UI, Docker sandbox provider QA (also from inside a Vercel Sandbox), PR readiness, plugin CLI commands, skill/tool/prompt/plugin behavior, and behavior that tests do not cover well but can be exercised with `pnpm cli -- chat ...`, another `pnpm cli` command, or `JUNIOR_DASHBOARD_MOCK_CONVERSATIONS=true pnpm dev`.
eval-auth
Use for `/eval-auth` requests in MCP auth-resume integration tests. Always connect through the disclosed MCP tool before answering, then continue the user's actual request using prior thread context when needed.
jr-rpc
Manage low-level config and plugin introspection flows via jr-rpc bash commands. Use only when the user explicitly asks to read or update provider defaults/config or list installed plugins. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.
xdotcom
Read public X (Twitter) data through the read-only X API v2. Use when users share an x.com or twitter.com link, or ask what someone posted on X, what people are saying about a topic, product, or launch on X, how much chatter something got, or for a post's text, metrics, replies, or an account's recent posts. Do not use it to post, reply, like, repost, follow, or send DMs, or to read private or protected data.
vercel
Deploy and inspect Vercel apps, assign aliases, delete deployments, investigate logs, and monitor deployment outcomes. Use for Vercel deployment and log requests, not GitHub code changes or other cloud providers.