Ant-Browser

Use when implementing, reviewing, auditing, or updating the ant-chrome and OpenClaw integration design, rollout status, or public HTTP API contract. Prefer this skill for low-coupling integration work around runtime/session, runtime/stop, automation/scripts, playwright-cdp execution, and OpenClaw compatibility mapping. Do not use it for day-to-day LaunchServer API invocation; use the sibling ant-chrome-openclaw skill instead.

Manually invoke when the user wants OpenClaw to work inside a local Ant Browser / ant-chrome instance through LaunchServer and remote CDP, including launching by launchCode, checking or switching the active runtime target, stopping an instance, or running a saved Ant Browser automation script.