Boundaries: lab vs Quicker product surfaces This repository is a public research lab . It must not absorb product private code or replace production browser control.
Surface
Visibility
Responsibility
QuickerOrg/agent-browser-lab (this repo)Public
CDP/Playwright/CLI experiments, observation protocol, comparison notes, start scripts
QuickerOrg/QuickerConnector Private
Production MV3 extension for Quicker users
QuickerHub/quicker-rpc (qkrpc)Public tooling
MCP/CLI including qkrpc_chrome_control / qkrpc_chrome_tabs; docs such as browser-automation boundaries
quicker-workspace Private workspace
Actions/subprograms/packages; may link to lab findings; must not host this lab under apps/
Public behavior of Connector / sys:chromecontrol (operations, MV3 constraints, “needs user cookies → extension”).
Links to qkrpc docs and getquicker KC chromecontrol pages.
Comparing lab CDP UX vs extension UX at a product-requirements level.
Copying Quicker Connector source, manifests, or private protocols into this repo.
Publishing user profiles, cookies, or authenticated HAR/screenshots.
Claiming agent-browser-lab is the official Quicker agent browser product.
Duplicating a full chromecontrol stack “for Cursor” when qkrpc_chrome_* already covers coarse user-browser ops.
Lab experiment → docs/matrix.md + experiment README
→ optional: quicker-workspace skill / docs pointer
→ optional: qkrpc browser-automation.md cross-link
→ only if productized: separate product repo or Connector/qkrpc change (not this lab)
Agent routing (for humans and coding agents)
Need
Go to
Research CDP / snapshot protocol / CLI bake-off
This lab
Control user's logged-in Chrome from Quicker actions
Connector + sys:chromecontrol
Control user's Chrome from Cursor MCP
qkrpc_chrome_* (Quicker running + extension connected)
Package / action editing in workspace
quicker-workspace (not here)
Lab profile path: %LOCALAPPDATA%\QuickerOrg\agent-browser-lab\...
Do not reuse Quicker's application data roots for lab browsers.