← ClaudeAtlas

panerelay-browser-uselisted

Use Browser Use and Browser Harness through Panerelay in the user's existing Chrome session and explicitly authorized tabs. Use when the user asks Browser Use to operate their current browser, reuse its login or extensions, or work in a tab authorized through the Panerelay side panel.
F-loat/panerelay · ★ 31 · AI & Automation · score 80
Install: claude install-skill F-loat/panerelay
# Panerelay Browser Use Run the normal Browser Use CLI through the exact setup-managed Panerelay CLI below. Browser Use retains page automation semantics; Panerelay supplies an Extension-backed virtual CDP connection to authorized tabs. ```text {{PANERELAY_BROWSER_USE_CLI}} ``` ## Workflow 1. Use the saved Direct or Extension mode unless the user requests an override. Setup initially saves Extension mode. Inspect or change the durable Panerelay-owned preference only when useful: ```bash {{PANERELAY_BROWSER_USE_CLI}} connection use browser-use extension {{PANERELAY_BROWSER_USE_CLI}} connection use browser-use direct ``` 2. In Extension mode, ask the user to open the Panerelay side panel and authorize the required current tab or site if no eligible tab is available. Browser focus is not authorization. Do not enable Chrome Remote Debugging, restart Chrome with debugging flags, widen authorization, or switch browsers after a denial. 3. Invoke Browser Use through the private run surface and keep upstream arguments and standard input unchanged: ```bash {{PANERELAY_BROWSER_USE_CLI}} run browser-use -- {{BROWSER_USE_EXECUTABLE}} <<'PY' print(page_info()) PY ``` Use the usual Browser Harness helpers such as `new_tab`, `list_tabs`, `page_info`, `wait_for_load`, `cdp`, `js`, `click_at_xy`, `iframe_target`, and `close_tab`. Prefer one cohesive heredoc for one task so shared page state cannot interleave between separate calls. 4. Override one invoca