agentsclimarketplace

Agent browser wsl2 setup

Skill ArthurZakirov/AgentDesk/skills/agent-browser-wsl2-setup

Make any machine ready for human and AI-agent work.

Install
npx -y skills add ArthurZakirov/AgentDesk --skill agent-browser-wsl2-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Install and configure `agent-browser` on a Windows machine with WSL2 after a browser path is already working. Use when a user wants the `agent-browser` CLI, its downloaded runtime, the `vercel-labs/agent-browser` repository, or an `agent-browser` attachment to a Windows host browser bridge from WSL2.

SKILL.md

3.4 KB, 736 tokens by cl100k_base, as published. Nobody here has run it

Agent Browser WSL2 Setup

This skill owns agent-browser setup only.

Browser availability belongs in $wsl2-browser-setup. Use that skill first if neither of these is already true:

  • native Linux google-chrome inside WSL2 works for real browsing and sign-in
  • a Windows host browser bridge is reachable from WSL2 on /json/version

Bootstrap Split

On a new machine, run these two commands directly from the AI:

npm install -g agent-browser
agent-browser install

Then have the human run this interactive command:

npx skills add vercel-labs/agent-browser

Important:

  • npm install -g agent-browser is non-interactive and should be run by the AI when possible
  • agent-browser install is non-interactive and should be run by the AI when possible
  • npx skills add vercel-labs/agent-browser is interactive and should be run by the human

After the human finishes the interactive npx skills add ... flow, continue with the runtime setup script.

Runtime Setup

Run:

bash "${CODEX_HOME:-$HOME/.codex}/skills/agent-browser-wsl2-setup/scripts/setup-agent-browser-runtime.sh"

The script:

  • installs agent-browser if missing
  • runs agent-browser install if needed
  • clones vercel-labs/agent-browser if missing

Mode A: Native WSL Browser

If the browser path from $wsl2-browser-setup is native Linux Chrome inside WSL2, test agent-browser directly:

agent-browser doctor --offline --quick
agent-browser open https://example.com
agent-browser snapshot -i -c

If this still hangs even though manual browsing works, stop debugging the browser here and use Mode B.

Mode B: Windows Host Browser Bridge

If the browser path from $wsl2-browser-setup is a Windows host browser bridge, attach agent-browser to that existing CDP endpoint:

bash "${CODEX_HOME:-$HOME/.codex}/skills/agent-browser-wsl2-setup/scripts/connect-windows-browser.sh" --session windows-host --bridge-port 9333
agent-browser --session windows-host get title
agent-browser --session windows-host snapshot -i -c

This was the proven control path before the native browser path was cleaned up.

Legacy Combined Wrapper

scripts/setup-agent-browser-wsl2.sh still exists as a compatibility wrapper for the older one-shot Windows bridge flow.

Prefer the split skills instead:

  1. $wsl2-browser-setup
  2. $agent-browser-wsl2-setup

Bundled Resources

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.