代理浏览器
- 作者仓库星标 68,946
- 作者仓库 paperclip
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @paperclipai · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
# Agent Browser
Use a controlled browser to verify behavior, capture evidence, or extract information from web pages that a static fetch cannot reach (SPAs, login-gated pages, dynamic content). This skill is about supervised verification, not unattended scraping.
## When to use
- You need a screenshot of a deployed page or a local dev server to confirm a UI change.
- You need to read JavaScript-rendered content that `curl`/`wget` will not see.
- A user reports a UI bug and you need to reproduce it interactively to capture console errors, network requests, or layout state.
- You need to walk through a short flow (load page, click, observe) to verify acceptance criteria.
## When not to use
- The page is reachable as static HTML. Use `curl`/HTTP fetch — it is cheaper, faster, and more reliable.
- The task is unattended large-scale scraping. That belongs to a dedicated scraper with rate limits, robots.txt handling, and a real user agent policy — not this skill.
- The site is behind authentication you do not own credentials for, or whose terms of service prohibit automation.
- The site involves sensitive accounts (banking, healthcare, government) where automation risks lockout or compliance issues.
## Before launching the browser
- Confirm the URL and what state should be true after navigation.
- Decide what evidence is needed: full-page screenshot, viewport screenshot, console log, network trace, HTML snapshot, extracted text.
- Decide the viewport size that matters for the task (mobile vs desktop). Default to a desktop size unless the task is mobile-specific.
- For local dev servers, confirm the server is running and the port is what you expect.
## Driving the browser
A typical verification session:
1. **Launch with a real-looking user agent** when the target is the public internet; an unrealistic UA flags automation traffic.
2. **Set a sane viewport** (e.g., 1366×768 desktop, 390×844 iPhone-ish).
3. **Navigate and wait for the right signal.** Prefer waiting for a specific selector or network-idle over arbitrary sleeps.
4. **Capture evidence immediately** after the wait condition succeeds, before any interaction perturbs the state.
5. **Interact deliberately.** One click at a time, with a wait between actions; re-screenshot after each meaningful state change.
6. **Read the console and network panels** for unexpected errors, 4xx/5xx responses, or slow requests.
7. **Close the browser cleanly** when done. Long-running browser sessions leak memory and hold ports.
## What evidence to record
For a verification task, deliver:
- A full-page or viewport screenshot of each meaningful state.
- The console log, filtered to warnings/errors.
- Any non-2xx network response with the URL, status, and a short response body excerpt.
- A short narration: "Navigated to X, observed Y, clicked Z, observed W."
For a UI bug repro, also record:
- The exact reproduction steps the user can follow.
- Viewport size and (where relevant) device pixel ratio.
- Whether the bug reproduces on first load vs after interaction.
## Login-gated pages
- Prefer programmatic auth (API token, magic link) over UI login.
- If UI login is the only path, the user must provide credentials explicitly for this run. Never reuse credentials outside the session.
- Do not store credentials in the session log, screenshot, or returned output.
## Performance and politeness
- Throttle to one navigation per few seconds when touching shared infra.
- Respect `robots.txt` for public sites you are inspecting at any volume.
- Cancel navigations if a page exceeds a reasonable timeout (e.g., 30s); the page is broken or rate-limiting you.
- Do not retry forever on failure. Retry once with a longer timeout, then escalate.
## Common failure modes
- **Selector not found.** Page changed, or you are waiting before render. Take a screenshot to see actual state; adjust the selector.
- **Click does nothing.** The element is offscreen, covered by a modal, or in a shadow DOM. Scroll into view or pierce the shadow root.
- **Headless detection.** Some sites detect headless Chrome and serve a different page. Use a non-headless mode or a fingerprint-realistic configuration only when authorized.
- **Cross-origin iframe blocking.** Iframes you do not own cannot be inspected; the page must offer the data outside the iframe or the task is infeasible.
## Anti-patterns
- Long unsupervised browser sessions that drift from the original task.
- Scraping behind authentication you do not own.
- Captioning a screenshot with "looks good" without saying what state was loaded and what selectors confirmed it.
- Treating a passing screenshot as proof of correctness across viewports you did not actually test.
章节与文件索引
按说明文件中的顺序排列。
何时使用
何时不使用
启动浏览器之前
驱动浏览器
记录什么证据
文件/命令 -> curl · wget · robots.txt · 4xx/5xx · warnings/errors.
内容校验值 -> 66b0cf77f7bb
当前原文的自动摘译,尚未人工审校。
何时使用
您需要已部署页面或本地开发服务器的屏幕截图来确认 UI 更改。您需要阅读
curl/wget看不到的 JavaScript 渲染内容。用户报告 UI 错误,您需要以交互方式重现它以捕获控制台错误、网络请求或布局状态。您需要完成一个简短的流程(加载页面、单击、观察)来验证验收标准。何时不使用
该页面可作为静态 HTML 访问。使用
curl/HTTP 获取——它更便宜、更快、更可靠。任务是无人值守的大规模抓取。这属于具有速率限制、robots.txt 处理和真正的用户代理策略的专用抓取工具,而不是这项技能。该网站支持您不拥有凭据的身份验证,或者其服务条款禁止自动化。该网站涉及敏感账户(银行、医疗保健、政府),其中自动化存在锁定或合规问题的风险。启动浏览器之前
确认 URL 以及导航后应处于何种状态。确定需要什么证据:全页屏幕截图、视口屏幕截图、控制台日志、网络跟踪、HTML 快照、提取的文本。确定对任务(移动与桌面)重要的视口大小。默认为桌面大小,除非任务特定于移动设备。对于本地开发服务器,请确认服务器正在运行并且端口符合您的预期。
驱动浏览器
典型的验证会话:当目标是公共互联网时,使用真实的用户代理启动;不切实际的 UA 标记自动化流量。设置一个合理的视口(例如,1366×768 桌面,390×844 iPhone 左右)。导航并等待正确的信号。更喜欢等待特定的选择器或网络空闲而不是任意睡眠。在等待条件成功后、任何交互扰乱状态之前立即捕获证据。
记录什么证据
对于验证任务,请提供: 每个有意义状态的整页或视口屏幕截图。控制台日志,过滤为警告/错误。任何带有 URL、状态和简短响应正文摘录的非 2xx 网络响应。简短的旁白:“导航至 X,观察 Y,单击 Z,观察 W。”