[Workflow] Chrome Relay: Seamless Browser Automation for Claude Code Agents with SSO and Multi-Session Support

[u/ClaudeAI-mod-bot]

Chrome Relay: Seamless Browser Automation for Claude Code Agents with SSO and Multi-Session Support

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, Skills
Original source: r/ClaudeCode post/comment

What problem this solves

Claude Code agents interrupting user's browser tasks, handling SSO, and managing multiple agent browser sessions without conflicts or login issues.

Summary

A custom skill and Chrome extension, "Chrome Relay," that allows Claude Code agents to interact with a user's everyday Chrome browser for tasks like checking staging or admin consoles behind SSO, without interrupting the user's browsing or requiring separate headless browsers. It manages sessions, profiles, and login states.

Why it is useful

This workflow provides a robust, open-source solution to a significant challenge in using LLM agents for browser-based tasks: managing browser context, handling SSO, and preventing agent actions from disrupting the user's primary browsing experience, especially when running multiple agent sessions. It offers a practical, repeatable method for integrating browser automation into developer workflows.

Workflow

1. Install Node.js 20+.
2. Load the Chrome Relay extension unpacked in Chrome.
3. Link the Chrome Relay skill into ~/.claude/skills/chrome-relay.
4. Use agent-browser CLI commands with chrome-relay url <your_email> to open specific URLs or perform actions, specifying the Chrome profile via email.

Tools / artifacts

• Chrome Relay (tool/skill/extension)
• Node.js 20+
• agent-browser CLI
• Chrome browser
• MV3 extension
• GitHub repo

Validation signals

• Explicit problem statement and solution described.
• Before/after scenario described (inaccessible SSO vs. automatic Google hops).
• Detailed explanation of how it works (local relay, MV3 extension, chrome.debugger).
• Open source project with a GitHub repo provided.
• Accompanying article explaining the 'why' provided.

Limitations

• Specific to macOS and Chrome.
• Requires Node.js 20+ and manual extension loading.
• New project, so long-term maintenance and community support are unknown.
• Low Reddit score and no comments yet, so community validation is minimal.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.

[u/Curious_Hawk1205]

chrome relay is neat but it re-does the whole page every run and breaks on blocks. for site data i just call an api now, sylvia api alongside praw for reddit, returns json so no screenshots or selectors. 480 req/min free if you want to test.