Skip to main content
Agent skill

Maxxing Browser

Turn on, set up, explain or troubleshoot the Harness Browser - a Chromium on this server that sessions and agents drive for sites without an API (sign-ins, forms, clicks, dashboards), that the user watches and takes over in a window (Settings -> Browser). Use when the user wants Claude to open a site, sign in somewhere, fill in a form or click through a page; when the mcpmaxxing-browser tools are missing ("you have no browser"); when a page is refused, a site blocks the browser, a connection (phone, proxy, WireGuard) is offline; or when the user asks where the browser, its profiles or its connections are.

All install options
Quick install · Personal (~/.claude/skills)Project / Cursor / Desktop →
mkdir -p ~/.claude/skills/maxxing-browser && curl -fsSL 'https://raw.githubusercontent.com/makushingu/harness-maxxing/main/skills/maxxing-browser/SKILL.md' -o ~/.claude/skills/maxxing-browser/SKILL.md

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Maxxing Browser when an AI agent needs a reusable SKILL.md workflow for this job: Turn on, set up, explain or troubleshoot the Harness Browser - a Chromium on this server that sessions and agents drive for sites without an API (sign-ins, forms, clicks, dashboards), that the user watches and takes over in a window (Settings -> Browser). Use when the user wants Claude to open a site, sign in somewhere, fill in a form or click through a page; when the mcpmaxxing-browser tools are missing ("you have no browser"); when a page is refused, a site blocks the browser, a connection (phone, proxy, WireGuard) is offline; or when the user asks where the browser, its profiles or its connections are.

When not to use it

Skip Maxxing Browser when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
One-line install (Claude Code)
mkdir -p ~/.claude/skills/maxxing-browser && curl -fsSL 'https://raw.githubusercontent.com/makushingu/harness-maxxing/main/skills/maxxing-browser/SKILL.md' -o ~/.claude/skills/maxxing-browser/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/maxxing-browser/SKILL.md. For a shared project, commit the folder at .claude/skills/maxxing-browser/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Maxxing Browser skill for this task: Use Maxxing Browser when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Harness Browser

One Chromium per **profile** on this server (sign-ins + the connection it goes out by). Each project has its own profile, **General** is the user's own (also the projects `general` and `system`). Every session and every agent gets **its own browser** inside its profile: it sees only its tabs. Docs: `docs/user/33-browser.md` (Docs -> Harness Browser).

Where it is in the UI (name it in the user's language, as the UI shows it: in French **Réglages -> Fonctionnalités -> Harness Browser**, **Réglages -> Navigateur**, **Regarder**): - **Settings -> Features -> Harness Browser**: the feature switch, **Set up** once; - **Settings -> Browser**: My browser, Profiles, Connections, how it works (asks, downloads, sleep); - the **Browser** line at the bottom of the sidebar, or Ctrl+K "my browser": the user's own browser, in a window; - in a session: the line above the message box, **Watch** = this session's browser in a window; - an agent: its info panel (its browser's picture, its profile); a project or a topic: its **...** menu -> **Browser...**.

## Use it only when nothing simpler works Read a page with WebFetch, `curl`, an API or the `web-scraping` skill first: faster, cheaper (the browser tools cost about 5k tokens a turn). The browser is for JavaScript-only pages, sign-ins, forms and clicks.

## The tools are missing in this session Check, in this order: ```bash maxxing browser status # feature on/off, what is missing on the server maxxing browser show <p>/<t> # what this folder gets, and where it comes from (project, topic, agent) ``` 1. **Feature off**: ask the user, then `maxxing browser enable` (installs what is missing as root, about a minute, then switches it on; the same as Settings -> Features -> Harness Browser -> Set up). Never on your own. 2. **Turned off for this project or topic**: the user's choice; `maxxing browser set <p>/<t> on` only if they ask. 3. **An agent**: off until its owner turns it on (its settings -> Browser, or `maxxing browser set <p>/<t>/<agent> on`; the agent's own conversation asks with `maxxing agents set <itself> browser.enabled=true`). 4. Then say: **the tools come at the next message** (a turn's tools are fixed when it starts).

## Sign-ins, captchas, codes - Never ask the user for a password in the chat. Call `ask_human` (the user gets a notification, Telegram too, and the window opens on the tab; it waits 30 min by default), or tell them: **Watch** above the message box, then sign in in the page. Sign-ins stay in the **profile**: every session and agent of the project has them after. - To sign in once for a whole project ahead of time: Settings -> Browser -> the project's profile -> open it. - Tabs the user opened in your browser are marked: leave them alone.

## When it goes wrong | Symptom | What to do | |---|---| | "not set up on this server" | `maxxing browser setup` (root), or **Set up** in Settings -> Features | | A page refused (agent in its sandbox) | only its domains: the notification **Add this domain**, or `maxxing agents set <path> domains='["example.com"]'` (owner) | | A page refused (anyone) | this server, local networks, raw IPs, `file:` and Chromium pages are refused on purpose | | Google "unusual traffic" | Google spots a driven Chromium, not the address: the search engine setting (⋮ menu of the window) -> DuckDuckGo or Bing | | A site blocks the browser | Settings -> Browser -> the profile's connection -> **Test** (the eye = the address sites see); **Data center** => a phone (Tailscale), a home box (WireGuard) or an ISP proxy | | "the connection is down" | stop using the browser and say so; the session shows **Go on when it is back** / **Retry now** | | Tailscale phone never online | the phone on, same account, **Run as exit node** on, **and** the exit node approved in the Tailscale admin console (machine -> Edit route settings -> Use as exit node) | | "profiles are in use right now" | 3 run at once by default: wait, or `maxxing browser settings --max-profiles N` | | Server slow | `maxxing browser settings --tab-sleep MIN --max-tabs N`, or put tabs to sleep from the window |

## Commands (owner only: refused in an agent's runs) ```bash maxxing browser enable | disable # the feature maxxing browser set acme on|off|inherit # a project (acme/blog = a topic) maxxing browser set acme/blog/writer on [--profile shop|inherit] # an agent, optionally on another profile maxxing browser profile add Shop [--exit phone] # a profile of its own (sign-ins apart) maxxing browser exit test phone|direct # what the sites see maxxing browser forget <id> # erase a profile's sign-ins, tabs and journal ``` Connections (Tailscale, proxy, WireGuard) are added in Settings -> Browser -> Connections: their passwords go to the vault, never in a file or the chat.

Intended uses

  • Use Maxxing Browser when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.