AunySillyMelean-browser-use
Documentation

From docs/install.md · e31dc91 · Built 2026-11-17

Install

Use Node 20 or newer. From a terminal:

npx lean-browser-use

The installer prints its plan, then asks Proceed? [Y/n] on a terminal. Non-interactive runs proceed automatically; --yes also skips the prompt. Undo the install with npx lean-browser-use --uninstall.

Choose the target

The config directory is selected by --claude-dir DIR, then $CLAUDE_CONFIG_DIR, then ~/.claude. --project targets ./.claude in the current project. Use one explicit target choice per invocation.

npx lean-browser-use install --project
npx lean-browser-use install --claude-dir ./sandbox-config --dry
npx lean-browser-use install --with-reader --yes
Install flagEffect
--claude-dir DIRUse the named Claude config directory.
--projectInstall into the current project's .claude.
--no-hooksCopy the hooks and print registration to paste by hand; skip the settings merge.
--with-readerAlso copy the optional reader and SearXNG files.
--dryPrint the real plan while leaving files unchanged.
--yesProceed after the plan without an interactive confirmation.
--helpPrint command usage.
--versionPrint the package version.

Files and settings

Here <cfg> means the selected config directory.

DestinationContents
<cfg>/skills/lean-browser-use/Method entrypoint and focused references.
<cfg>/agents/aun-browser-runner.mdBrowser subagent definition.
<cfg>/lean-browser-use/hooks/Guard and cleanup scripts and registration source.
<cfg>/lean-browser-use/briefs/Browser and cheap-helper packet templates.
<cfg>/lean-browser-use/reader/Optional compile-once reader and specs.
<cfg>/lean-browser-use/searxng/Optional search script and container configuration.
<cfg>/lean-browser-use/manifest.jsonInstall-time hashes, created directories, and settings changes.
<cfg>/settings.jsonMerged hook registrations, preserving other settings and hooks.
<cfg>/settings.json.lean-browser-use.bakBackup of existing settings, written only if the backup is absent.

Repeated installs avoid duplicate registrations. The installer substitutes real hook paths into the registration template. It never installs third-party tools, runs a vendor login, contacts the network, or prints secrets. Optional tool installation belongs to the user; see reader and search.

Activate and inspect

Start a fresh Claude Code session so it can discover the installed skill and agent. Ask it to use lean-browser-use for a browser task. Pick your Chrome profile by name when logged-in work needs it. A Chrome connection and tool permissions come from your own Claude Code setup.

npx lean-browser-use doctor
npx lean-browser-use doctor --claude-dir ./sandbox-config --json

Doctor checks installed file hashes, registered hook paths, executable shims, synthetic hook responses, and leased processes still running (see cleanup). Edited files are reported. Its capability table explains what Python, crwl, Docker, Claude Code, and local transcripts enable; missing optional tools are capabilities to add, not installation errors. JSON output has ok and checks, each with id, status, and detail. Hook behavior on your Claude Code version is confirmed by npx lean-browser-use doctor.

Measure and remove

npx lean-browser-use measure --dir ./transcripts --since 2026-10-25 --json
npx lean-browser-use uninstall --claude-dir ./sandbox-config --dry
npx lean-browser-use uninstall --claude-dir ./sandbox-config

measure defaults to the selected config directory's projects folder; --dir overrides it, --since YYYY-MM-DD filters timestamps, and --json returns structured results. See the meter.

Uninstall compares each file with its install-time hash. It removes matching files, preserves and lists edited files, removes only its hook entries from settings, and removes only empty directories this install created. It refuses traversal, absolute manifest paths, and symlink entries. The manifest is removed last. Follow printed manual steps for registration pasted by hand. For a project install, point uninstall and doctor at --claude-dir ./.claude.

ExitMeaning
0Success.
1A check failed.
2Usage error or refused target; a missing uninstall manifest names its path.
3Uninstall preserved edited files.