QA testing - verify by actually driving it

After you build or change an app or website, do not assume it works. Drive it and check.

1. Network is required - check it first

Installing these tools and loading pages need outbound network, which sandboxes can block. Check before anything else:

curl -fsI https://github.com >/dev/null 2>&1 && echo "network ok" || echo "network blocked"

If it prints network blocked, stop and tell the user:

I need network access to install and run the testing tools. Run /permissions and choose an access level that allows network, then ask me again.

2. Web apps and websites - agent-browser

On macOS/Linux, prefer the prebuilt binary directly:

if ! command -v agent-browser >/dev/null; then
  os=$(uname -s | tr '[:upper:]' '[:lower:]'); m=$(uname -m)
  case "$os/$m" in
    darwin/arm64)              asset=agent-browser-darwin-arm64 ;;
    darwin/x86_64)             asset=agent-browser-darwin-x64 ;;
    linux/aarch64|linux/arm64) asset=agent-browser-linux-arm64 ;;
    linux/x86_64)              asset=agent-browser-linux-x64 ;;
  esac
  mkdir -p ~/.local/bin
  curl -fL "https://github.com/vercel-labs/agent-browser/releases/latest/download/$asset" -o ~/.local/bin/agent-browser
  chmod +x ~/.local/bin/agent-browser
fi
agent-browser install
agent-browser skills get core

On Windows, use the package installer because it downloads the matching native binary:

if (-not (Get-Command agent-browser -ErrorAction SilentlyContinue)) {
  npm install -g agent-browser
  $env:Path = "$env:APPDATA\npm;$env:Path"
}
agent-browser install
agent-browser skills get core

Then use the tool's maintained guide: agent-browser open <url>, take a snapshot, act on the element refs, and snapshot again.

3. Native desktop apps - cua-driver

macOS/Linux: