Chrome Extension Relay Helper - Mac
ReviewAudited by ClawScan on May 10, 2026.
Overview
This helper is transparent about its purpose, but it can force-close and reconfigure Chrome while enabling automation in your real logged-in Chrome session.
Install or run this only if you intentionally want OpenClaw to control a live Chrome session. Close or save important Chrome work first, consider using a separate Chrome profile with limited logins, and verify the Peekaboo dependency before granting Accessibility permissions.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the helper can abruptly close your Chrome windows and change browser startup/session state, which could disrupt unsaved work or alter your normal browser behavior.
When not already attached, the script force-closes Chrome and writes to the user's Chrome Default profile Preferences file. This is disclosed in SKILL.md and related to the relay setup, but it is a broad local action with no prompt, backup, or rollback.
pkill -9 -f "Google Chrome" 2>/dev/null || true ... with open(p, "w") as f:
json.dump(prefs, f)Run it only when you are comfortable closing Chrome. The skill should ideally ask for confirmation before killing Chrome, avoid force-kill where possible, and back up or restore changed Chrome preferences.
After attachment, an agent using the chrome browser profile may interact with websites as you, including pages where you are already signed in.
The skill intentionally enables automation through the user's existing Chrome session, which may include logged-in accounts. The artifacts do not bound which sites, accounts, or actions downstream browser automation may use.
Once attached, the `browser(profile="chrome")` tool works — you can navigate, snapshot, click, and scrape using your real Chrome session.
Use this only for tasks where real-session browser access is intended. Prefer a separate Chrome profile with limited accounts, and review/confirm sensitive clicks, form submissions, purchases, or account changes.
Users may install and grant privileges to an external UI automation tool that is not reflected in the registry requirements.
The skill depends on an external Homebrew tap and macOS UI automation tooling. This is disclosed and purpose-aligned, but the registry metadata does not declare required binaries or an OS restriction.
macOS only. Requires Peekaboo (macOS UI automation CLI). ... brew install steipete/tap/peekaboo
Verify the Peekaboo package source before installing, and the skill publisher should declare the macOS restriction and required dependency in metadata.