qz Browser Agent: Research and Reusable Tasks in Your Own Chrome
Purpose, mechanisms, getting started and boundaries
Source: alibaba/qz-browser-agent · alibaba
User Problem
Positioning and task fitWeb research often needs login state, cross-site navigation, dynamic content and source tracking. qz puts an agent in the everyday browser sidebar, where users can observe execution and external coding agents can delegate whole tasks through CLI or MCP. Its defining choice is to reuse the local browser environment.
- Build sourced research tables across websites
- Work with pages visible in an existing signed-in session
- Save recurring research as a reusable skill
Product Mechanism
Capabilities and execution- Sidebar and background have separate ownershipThe architecture assigns task state and persistence to Background, presentation to Side Panel and page operations to content scripts. UI visibility, task state and model calls belong to distinct layers and should be diagnosed separately. Source
- Delegate a goal rather than each clickAn external agent submits a goal and observes progress, questions and the result. CLI and MCP are connection surfaces; execution and persistence remain in the extension. Source
- Turn a working flow into a reusable procedureA completed task can be saved as a skill for later reuse. First review source selection, field definitions and failure handling so that an accidental success does not become a supposedly reliable procedure. Source
- Separate local state from model requestsSessions, skills and collected data stay locally, while users select a model provider. Local browser execution does not mean offline inference: task data can still reach the configured model and visited websites. Source
Workflow
Start with a small task- Install the extensionInstall from the README store link, open the sidebar and read the first-use disclosure. Establish a baseline on public pages before using signed-in workflows.
- Configure a modelConfigure a tool-capable provider and authenticate. Read one page and return its title and source to check both model access and browser execution.
- Define the deliverableSpecify objects, fields, time range and source requirements. Ask for unknown values to remain empty or marked rather than guessed.
- Review before connecting another agentAfter a sidebar task works, pair the CLI and inspect streamed results and table sources. Save the procedure as a skill only after review.
The trial sequence and checks are editorial guidance. Entry commands follow official documentation; this project was not executed for the article. Source
Official entry example
npx qz-browser-agent@latest connect
npx qz-browser-agent@latest create "Compare the official feature pages of two tools and return source links" --streamComplete the prerequisites above first. Examples contain no real credentials.
Limits and Boundaries
Constraints and selection| Boundary | Meaning | Suggested action |
|---|---|---|
| Browser differences | The README distinguishes Chrome, Edge and Firefox release and development status. Source | Choose the documented package and distinguish temporary loading from a signed store release. |
| Cost and access | Extension licensing and model costs are separate, and tasks inherit the browser’s visible access. Source | Limit task scope and review data before a consequential submission or modification. |
Scroll horizontally to view the full table
qz fits research that needs real browser context. For public static pages, simpler HTTP extraction may already meet the requirement.
How to Evaluate Adoption
Trial scenario and verificationStart by comparing two official feature pages with columns for capability, limitation and source URL. Require every conclusion to trace to a page and list unverified fields separately. Add signed-in dashboards later. This staged trial separates reasoning errors, website differences and execution problems.
Check completion state, resolved follow-up questions, readable exports and agreement between key cells and their sources. A polished table alone is not verification.
Evidence: Pinned README · Supporting official documentation · Current repository。
Source fetched (UTC): 2026-11-02T07:26:40.908Z；snapshot commit: 1aaa6ee2d1fb。The source date denotes the repository snapshot commit, not the project’s original launch.