By name: quicker-chromecontrol description: "Control the user's real browser (Quicker Connector) via user_browser / qkrpc_chrome_control RPC, or author sys:chromecontrol steps in actions."
quicker-chromecontrol
Route for browser automation against the user's logged-in browser.
See also: docs/browser-automation.md — unified boundary table (Playwright / embedded / extension).
Agent vs action browser
QuickerAgent browser |
user_browser / qkrpc_chrome_control |
sys:chromecontrol steps | |
|---|---|---|---|
| Who runs | Agent Playwright session | Agent via RPC → Quicker extension | User's action at runtime |
| Login state | None (clean profile) | User's cookies / login | User's cookies / login |
| Needs extension | No | Yes (Quicker Connector) | Yes |
| Use for | Agent reads arbitrary URL while designing | Agent operates user's open browser in chat | Production automation in saved actions |
Live control (agent in chat)
user_browser({ action: "tabs" })or MCPqkrpc_chrome_tabs— list connected tabsuser_browser({ action: "run", operation: "OpenUrl", parameters: { url, windowId: "New", waitComplete: true } })- Reuse
sessionId;tabIdfrom OpenUrl is auto-carried when omitted on next run - CLI:
qkrpc chrome run --operation RunScript --params '{"script":"document.title"}' --json
Parameter schema: qkrpc_step_runner_get with key=sys:chromecontrol and controlField = operation.
Authoring actions (on disk)
qkrpc_step_runner_search→sys:chromecontrolqkrpc_step_runner_getwithcontrolField= operationdocs({ action: "get", topic: "chromecontrol-authoring" })- Patch:
reference: "examples/chromecontrol"
Hard rules
- Reuse tabId across steps (
tabId.varin actions; literaltabIdor session in RPC) - RunScript on MV3: user must enable extension Allow user scripts
- Prefer BackgroundCommand over legacy BackgroundScript on MV3
- Do not guess
inputParamskeys — always step_runner_get first
Related
quicker-browser-script (page script + trigger auto-run pipeline) · quicker-authoring · qkrpc · browser (Playwright, no login)