Skip to content
Development
Skill

/cm-browse

Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native browser mode — prefer the host browser first.

From plugin
cm
5262 skills8 agents11 commands3 hooks
+1
Install
$ npx -y skills add tody-agent/codymaster --skill cm-browse --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/cm-browse

Context preview

The summary Claude sees to decide when to auto-load this skill.

Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native browser mode — prefer the host browser first.

SKILL.md

cm-browse.SKILL.md
name: cm-browse
description: "Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native browser mode — prefer the host browser first."

cm-browse — local Playwright daemon (fallback)

> **Prefer the host browser.** Per [_shared/browser-strategy.md](../_shared/browser-strategy.md): > on Claude Code / Antigravity / Cursor / Codex, drive the platform's **native browser mode** > (Claude in Chrome, Claude Preview, Chrome DevTools / Playwright MCP). This daemon is the > **fallback for bare CLI hosts with no browser mode**, and is **never auto-started** — suggest > it to the user and let them opt in. > > **Full runbook:** [docs/browse-daemon.md](../../docs/browse-daemon.md) (install Chromium, token, troubleshooting).

When to use

  • **Only** when no host browser mode is available (bare CLI) and you genuinely need a real

browser for visual QA, screenshots, or post-deploy smoke. Otherwise use the host browser.

  • HTTP-only checks (status code, `curl`) need no browser — do those first.

CLI

export CM_BROWSE_TOKEN="$(openssl rand -hex 24)"
cm browse start --port 17395 --token "$CM_BROWSE_TOKEN"

HTTP API (Bearer token)

  • `POST /session/start` body `{ "headless": true }`
  • `POST /navigate` `{ "url": "https://…" }`
  • `POST /refs/refresh` — assigns `data-cm-ref` to interactive nodes; use `@e1` style refs.
  • `POST /click` `{ "ref": "e1" }`
  • `POST /fill` `{ "ref": "e2", "value": "text" }`
  • `GET /screenshot` — PNG
  • `GET /console` / `GET /network` — ring buffers

Integrations

  • `cm qa-visual --url …` calls the daemon locally.
  • Pair with `cm-canary` / `cm-safe-deploy` for ship verification.
Read more
Ships withcm

"I can't write code. But in 6 months, I shipped 12 real products using AI. CodyMaster is everything I learned — so you don't have to repeat my mistakes." — Tody Le, Head of Product, Creator of CodyMaster 50+ skills. One install.

Get the whole plugin

Other skills on cm.