kachilu-browser — Claude Code plugin: what it does, how to install
The kachilu-browser plugin for Claude Code and Codex automates browser tasks, detects CAPTCHA and Cloudflare challenges, and routes completion through a local flow; from WSL2 it drives a Windows browser.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install kachilu-browser@awesome-codex-pluginsWhat kachilu-browser does
The plugin gives an agent a browser it can actually operate: loading pages, clicking, typing. reCAPTCHA v2/v3 and Cloudflare Turnstile get recognised, and completion is routed into the local CLI and browser. Built for Claude and Codex.
Setup starts with npm install -g kachilu-browser, followed by kachilu-browser onboard. An interactive terminal asks which host you want; a scripted run needs --target codex, --target claudecode or --target claudedesktop. When the remote debugging page opens, tick the permission box, otherwise the agent never connects. On WSL2 the full MCP onboarding writes the Windows connect target and locates your Windows profile on its own.
WSL2 support is the reason to pick this one: an agent running in Linux drives the same Windows browser you use every day. There is a catch. A raw kachilu-browser shell command can lose the Windows target variable and open a WSL-local browser instead, so keep prepare/exec as your route whenever the MCP tools are there. Everything runs locally, with no telemetry and no hosted relay.
What it helps with
- get past a reCAPTCHA wall without leaving the agent
- drive your Windows browser profile from a WSL2 agent
- keep the session alive across context compaction and resume
- wire up the MCP browser route with a single
onboardcall - identify which bot check a page is running
Example prompts for the agent
- Open the signup page with kachilu-browser and tell me what challenge it hits
- Log in through
kachilu_browser_execand keep the session for the next step - Attach to my Windows browser from WSL2 and pull the table off the page
How to install kachilu-browser
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install kachilu-browser@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about kachilu-browser
How do I install kachilu-browser in Claude Code?
Add the marketplace with /plugin marketplace add hashgraph-online/awesome-codex-plugins, then install the plugin: /plugin install kachilu-browser@awesome-codex-plugins.
What does kachilu-browser do?
It lets an agent navigate, click and type in a browser, and it recognises reCAPTCHA or Cloudflare Turnstile so the challenge is handled through the local browser flow.
What happens when a CAPTCHA appears?
The plugin detects the challenge and routes completion through the local CLI and browser flow, so the agent does not have to abandon the task.
Source text
kachilu-browser · MIT
# Kachilu Browser `kachilu-browser` is an anti-bot-aware browser automation CLI for AI agents such as Codex and Claude. <p align="center"> <img src="docs/reCAPTCHA.gif" alt="Kachilu Browser detecting a reCAPTCHA challenge" width="100%"> </p> > CAPTCHA in the way? The LLM detects it through the SKILL and hands off > completion automatically. Nothing complicated. Human-like interaction is the default. When reCAPTCHA v2/v3 or Cloudflare Turnstile appears, `kachilu-browser` detects the challenge and routes completion through the local CLI/browser flow. WSL2 is first-class: agents running in Linux can control the Windows-side browser profile you actually use, instead of a separate WSL-only browser. Free to use. Local by design. No hosted relay, no telemetry, no external control plane between the agent and your browser. ## Install ```bash npm install -g kachilu-browser kachilu-browser onboard ``` When this page appears, tick the checkbox so the agent can connect to your browser:  ## OpenClaw ```bash openclaw plugins install kachilu-browser openclaw gateway restart ``` OpenClaw uses the same npm package bundle, so no separate package name or extra install script is needed. ## Onboarding targets - If `--target` is omitted in an interactive terminal, `kachilu-browser onboard` prompts for the host target - In non-interactive runs, pass `--target codex`, `--target claudecode`, or `--target claudedesktop` - Use `--skill-only` or `--no-mcp` for desktop hosts that already provide a browser session and only need the Codex or Claude Code skill - For Codex and Claude Code on WSL2, full MCP onboarding persists `KACHILU_BROWSER_AUTO_CONNECT_TARGET=windows` and auto-detected `KACHILU_BROWSER_WINDOWS_LOCALAPPDATA` unless you override them - When targeting Windows browsers from WSL2 through MCP, `onboard` also ensures `%USERPROFILE%\.wslconfig` has `[wsl2] networkingMode=mirrored` and reports when `wsl --shutdown` is required - `codex`: writes `~/.codex/config.toml` and links `~/.codex/skills/kachilu-browser` - `claudecode`: writes `~/.claude.json` and links `~/.claude/skills/kachilu-browser` - `claudedesktop`: writes the Claude Desktop local MCP config. Use `claude-desktop` as an equivalent alias. - Claude Desktop Skills are distributed as `kachilu-browser-skill.zip` on GitHub Releases and must be uploaded through Claude Desktop's Skills UI. ```bash kachilu-browser onboard --target codex --codex-home <desktop-codex-home> --skill-only ``` ## MCP control plane Agents should keep using a host-provided browser session when one is explicit. Otherwise, they should keep using the MCP prepare/exec workflow whenever the tools are available, including after context compaction or resume. For MCP-managed sessions, this preserves the session, profile, and WSL2 Windows-browser target from the MCP env block. Raw `kachilu-browser` shell commands are a fallback for environments without MCP, explicit CLI requests, or intentional local WSL/Linux browser work. On WSL2, a raw shell command can miss `KACHILU_BROWSER_AUTO_CONNECT_TARGET=windows` and launch or control a WSL2-local browser instead of the intended Windows browser. Successful prepare and exec responses include `controlPlane: "mcp"` and `followUpTool: "kachilu_browser_exec"` so agents can preserve the MCP route across context compaction and long-running resumes. ## Release model - Native binaries are built from the private source repo. - The npm package bundles available native binaries so `npm install -g kachilu-browser` works without exposing the private source tree. - The source repo must provide `KACHILU_BROWSER_RELEASE_TOKEN` so it can create this repo's GitHub Release and push synced tags. - This public repo publishes the npm package via npm Trusted Publishing after the package already exists on npm. - The very first npm publish for `kachilu-browser` must be done manually with `npm publish --access public`. - If the package was unpublished, npm blocks republishing the same package name for 24 hours. - This repo's publish workflow also refuses to publish if the package does not yet exist on npm. - The npm package downloads matching native binaries from GitHub Releases only when the current platform binary was not bundled in the package. ## Commands ```bash kachilu-browser --help kachilu-browser onboard --help node scripts/mcp-server.mjs ```
© Kachilu Inc. · MIT · hashgraph-online/awesome-codex-plugins