Unicli
olo-dot-io/Uni-CLI
Comprehensive guide to Uni-CLI — the open Agent-Computer Interface runtime for real software.
Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay.
Install Chrome Relay
$ npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aindeev/agent-chrome-relay chrome-relay --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aindeev/agent-chrome-relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill .claude/skills/chrome-relay && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "chrome-relay" agent skill from https://github.com/aindeev/agent-chrome-relay/tree/main/skill into .claude/skills/chrome-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-relay", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aindeev/agent-chrome-relay/tree/main/skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aindeev/agent-chrome-relay chrome-relay --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aindeev/agent-chrome-relay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill .agents/skills/chrome-relay && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chrome-relay" agent skill from https://github.com/aindeev/agent-chrome-relay/tree/main/skill into .agents/skills/chrome-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-relay", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aindeev/agent-chrome-relay chrome-relay --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aindeev/agent-chrome-relay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill .cursor/skills/chrome-relay && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chrome-relay" agent skill from https://github.com/aindeev/agent-chrome-relay/tree/main/skill into .cursor/skills/chrome-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-relay", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aindeev/agent-chrome-relay.git --path skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aindeev/agent-chrome-relay chrome-relay --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aindeev/agent-chrome-relay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill .gemini/skills/chrome-relay && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chrome-relay" agent skill from https://github.com/aindeev/agent-chrome-relay/tree/main/skill into .gemini/skills/chrome-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-relay", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aindeev/agent-chrome-relay chrome-relayInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aindeev/agent-chrome-relay.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill .github/skills/chrome-relay && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chrome-relay" agent skill from https://github.com/aindeev/agent-chrome-relay/tree/main/skill into .github/skills/chrome-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-relay", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aindeev/agent-chrome-relay chrome-relay --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aindeev/agent-chrome-relay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill .opencode/skills/chrome-relay && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chrome-relay" agent skill from https://github.com/aindeev/agent-chrome-relay/tree/main/skill into .opencode/skills/chrome-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-relay", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chrome-relay- GitHub stars
- 249
- Token cost
- ~669 tokens
- SKILL.md length
- 254 words
- Files
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay.
- Tasks that involve Browser automation
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Authentication
What it does
Chrome Relay is an agent skill from aindeev/agent-chrome-relay. Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay. Load this BEFORE any browser step that needs their logins (internal tools, Google-SSO apps, GitHub, admin consoles, staging environments, OAuth consent screens) or when they say "check it in the browser", "open it logged in", "click through", "use my Chrome". Never drive their Chrome any other way.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Browser automation and Authentication. It works with GitHub, Chrome Extensions and macOS. The repository describes itself as: Let your AI agents use your Chrome, signed in as you, in background tabs. By Alexey Indeev · blog: read.aindeev.com · X: @AlexeyIndeev. The licence is MIT.
When your agent uses it
- Tasks that involve Browser automation
- Tasks that involve Authentication
Example prompts
- “check it in the browser”
- “open it logged in”
- “click through”
- “/chrome-relay”
What it can do on your machine
Read from SKILL.md and the folder at commit cf0f458. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chrome Relay loads about 669 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 254 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aindeev/agent-chrome-relay at commit cf0f458, republished under its MIT licence (© aindeev). 254 words, ~669 tokens.
Download SKILL.mdSave it as
.claude/skills/chrome-relay/SKILL.md (or your agent's skills folder).- name
- chrome-relay
- description
- Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay. Load this BEFORE any browser step that needs their logins (internal tools, Google-SSO apps, GitHub, admin consoles, staging environments, OAuth consent screens) or when they say "check it in the browser", "open it logged in", "click through", "use my Chrome". Never drive their Chrome any other way.
Chrome Relay
Chrome Relay lets Claude Code, Codex, Cursor and Paseo agents drive background tabs in the person's everyday Chrome, with their real logins. Your tabs open inactive in a collapsed "Agents" tab group, you only see and control tabs you opened, and nothing on their screen moves. ~0.15s per command.
export AGENT_BROWSER_SESSION=<your-agent-name> # one session per agent
chrome-relay identities # which profile (email) to use for what
agent-browser --cdp "$(chrome-relay url you@company.com)" open https://example.internal/
agent-browser snapshot -i # interactive elements with refs (text, cheap)
agent-browser fill @e3 "text"; agent-browser click @e5; agent-browser wait --text "Saved"
agent-browser get text main; agent-browser screenshot shot.png
agent-browser close # ALWAYS when done: closes your tabsRules:
- Pass
--cdponly on the first command of a session. The URL carries this Mac's secret: never print it into logs, PRs, chats or files. Only Claude Code, Codex, Cursor and Paseo processes are accepted. - If
chrome-relayis missing or a connect fails, runchrome-relay doctorand tell the person what it says. Setup is theirs to do (README of github.com/aindeev/agent-chrome-relay); never install it for them. - Google sign-in hops are automatic when the account is already signed in (account chooser, Continue/Allow).
- Never type credentials or pick accounts yourself. If a command fails with
SIGN-IN NEEDED: ...(password, passkey, 2-step, signed-out account) or you land on any login form: stop, ask the person to sign in in their own Chrome window for that profile, and retry after they confirm. - Popups and "open in new tab" links open as new hidden tabs that belong to you (
agent-browser tab list). - Everything you do is in the audit trail (
chrome-relay audit). Typed text is stored only as its length. - Never use
--auto-connect,--cdp 9222,--headed, Playwright attached to their Chrome, computer use or AppleScript against Chrome: those take over their screen. - Public pages that need no login: a plain headless
agent-browser open <url>(no--cdp) is fine.
© aindeev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skill of aindeev/agent-chrome-relay.
Open the folder on GitHubat commit cf0f458
Compare with similar skills
Chrome Relay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chrome Relay this skillaindeev/agent-chrome-relay | 249 | — | ~669 | Automated safety check: Pass | MIT | |
| Unicliolo-dot-io/Uni-CLI | 274 | — | ~3.8k | Automated safety check: Notes | Apache-2.0 | |
| Kane CLI Browser TestingLambdaTest/kane-cli | 249 | — | ~8.4k | Automated safety check: Pass | Apache-2.0 | |
| Claude in Chrome MCP Troubleshootingtrailofbits/skills | 7.5k | 3 repos | ~2.6k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Xiaohongshu HubOpenMinis/MinisSkills | 446 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Weibo HubOpenMinis/MinisSkills | 446 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Kane CLI Browser Testing
LambdaTest/kane-cli
Drives a real browser through the kane-cli tool and designs requirement-linked test suites from a PRD or a plain description, with mobile and cloud-grid runs.
- Official
Claude in Chrome MCP Troubleshooting
trailofbits/skills
Diagnoses why the Claude in Chrome MCP tools report the browser extension as not connected, with macOS-specific checks and a fix for the Claude.app native host conflict.
Xiaohongshu Hub
OpenMinis/MinisSkills
Skill for reading and writing Xiaohongshu (XHS) data using Python + UV.
Weibo Hub
OpenMinis/MinisSkills
A skill for reading and writing Weibo data with Python + UV.
- Official
Before And After
sanity-io/sanity
Add existing screenshots or screen recordings to a GitHub pull request as a before/after or preview block.
Related
Works with
Categories
Questions about Chrome Relay
What does Chrome Relay do?
Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay. Chrome Relay is an agent skill from aindeev/agent-chrome-relay. Use the person's own signed-in Chrome from the command line, in background tabs, through Chrome Relay.
When should I use Chrome Relay?
Chrome Relay fits situations like: tasks that involve Browser automation; tasks that involve Authentication.
How do I install Chrome Relay in Claude Code?
Run `npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a claude-code`. Or copy the skill folder (skill in aindeev/agent-chrome-relay) into .claude/skills/chrome-relay in your project. Claude Code loads it when a task matches its description.
How do I install Chrome Relay in Codex?
Run `npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a codex`. Or copy the skill folder (skill in aindeev/agent-chrome-relay) into .agents/skills/chrome-relay in your project. Codex loads it when a task matches its description.
Can I use Chrome Relay in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aindeev/agent-chrome-relay --skill chrome-relay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-relay, .gemini/skills/chrome-relay, .github/skills/chrome-relay and .opencode/skills/chrome-relay in your project.
What does Chrome Relay need to run?
SKILL.md names no scripts, command-line tools or credentials: Chrome Relay is instructions for the agent only.
Does Chrome Relay access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Chrome Relay safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Chrome Relay use?
Chrome Relay is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Chrome Relay use?
About 669 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Chrome Relay?
Skills that share tags, products or a category with Chrome Relay: Unicli (olo-dot-io/Uni-CLI, 274 stars), Kane CLI Browser Testing (LambdaTest/kane-cli, 249 stars), Claude in Chrome MCP Troubleshooting (trailofbits/skills, 7.5k stars) and Xiaohongshu Hub (OpenMinis/MinisSkills, 446 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chrome Relay?
aindeev (a GitHub user) maintains it in aindeev/agent-chrome-relay, which has 249 GitHub stars. The repository was last updated on October 11, 2026.
Source: aindeev/agent-chrome-relay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.