← Browser UseCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Browser Use
Snapshot Sep 30, 2026 · 23:17 UTC · version 0.13.10
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user asks to QA, test, evaluate, score, or inspect the quality and behavior of a website or web app in a browser.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 245
}
],
"name": "qa",
"skill_md_contents": "---\nname: qa\ndescription: Use when the user asks to QA, test, evaluate, score, or inspect the quality and behavior of a website or web app in a browser.\n---\n\n# Browser QA\n\nEvaluate a website or web app with an approved host-managed browser when one is available. The deliverable is a concise QA verdict backed by observed evidence.\n\n## Method\n\n1. Identify the target URL and the flow or quality dimension to test.\n2. Use only the browser capability already exposed by the host.\n3. Exercise the ordinary user-visible flow. Respect authentication, permissions, and access boundaries.\n4. Record observable failures, confusing states, broken interactions, and accessibility/usability issues.\n5. Score the tested experience from 1 to 5 and explain the evidence behind the score.\n\nDo not install browser tooling, create tunnels, alter network settings, import credentials, or attempt to defeat warnings or access controls.\n\nIf no browser capability is available, provide a QA test plan instead and state that live testing was not performed.\n"
}SHA-256 of public snapshot: 06c3d60e98e4792c4e914f9bab61218d7d7c8b1cb87489a4afeba3a704c5997e