← ClaudeAtlas

browser-relaylisted

Operate the user's existing, logged-in Chrome locally or on an explicitly connected remote machine. Read complete page content with actionable refs and links, perform grouped actions, and use screenshots in persistent browser sessions. Skip static public pages and pure REST APIs.
reliefeai/browser-relay · ★ 139 · AI & Automation · score 82
Install: claude install-skill reliefeai/browser-relay
# Browser Relay Use the user's existing browser and login state. Select an actual tab ID by URL and title; a foreground change must not redirect your work. ```bash browser-relay tabs browser-relay read --tab <id> --session <task-name> ``` Use a distinct session name for each independent task. Managed operations claim the tab for that session. Another owner must release or hand it off before you operate it; never stop someone else's session merely to gain access. These leases coordinate trusted clients, not access control against local software. ## Choose the observation that answers the question - **Reading:** `read` focuses on main content and preserves semantic groups, complete text and full URLs. `read --ref <ref>` reads an observed subtree. - **Operating:** `observe` includes the whole page, controls, states and refs. Use it to find navigation, dialogs or controls outside the main content. - **Seeing:** use screenshots for canvas, layout, missing accessible text or a semantic action with an unexpected outcome. In the runtime, `tab.observe({mode:'both'})` returns a snapshot and screenshot together. With CLI use `observe --mode both --output /tmp/page.png --tab <id> --session <name>`. Follow `nextCursor` (`read --cursor <cursor>`) when an observation is truncated. A cursor continues the same captured text; it is not a new live observation. After navigation it expires. If the page exceeds the cache limit, read a smaller subtree. Do not report a partial result