Codymaster cm-browse

Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright.

install
source · Clone the upstream repo
git clone https://github.com/tody-agent/codymaster
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/tody-agent/codymaster "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/cm-browse" ~/.claude/skills/tody-agent-codymaster-cm-browse && rm -rf "$T"
manifest: skills/cm-browse/SKILL.md
source content

cm-browse — local Playwright daemon

Full runbook: docs/browse-daemon.md (install Chromium, token, troubleshooting).

When to use

  • Visual QA, screenshots, post-deploy smoke through a real browser (not only Stitch/Pencil).
  • Before claiming “UI works”, drive
    cm browse
    +
    cm qa-visual
    .

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.