| name | ant-chrome-openclaw |
| description | 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. |
| when_to_use | Use this skill whenever the task mentions Ant Browser, ant-chrome, LaunchServer, launchCode, profileId/profileName selectors, runtime active/status/stop, attaching OpenClaw to an already running browser via remote CDP, or executing a saved Ant Browser automation script such as news-query-txt. This workflow can launch, stop, or mutate browser state, so prefer explicit invocation instead of silent automatic use. |
| compatibility | Designed for OpenClaw with same-host Ant Browser LaunchServer access. Requires loopback access to the LaunchServer base URL plus either curl or PowerShell for host-side HTTP calls. |
| disable-model-invocation | true |
| argument-hint | [goal-or-script] |
| metadata | {"openclaw":{"skillKey":"ant-chrome-openclaw","primaryEnv":"ANT_CHROME_API_KEY","requires":{"anyBins":"[Truncated]"}}} |
Ant Browser via OpenClaw
Invoke this skill explicitly when the user wants OpenClaw to control browser work that should run inside Ant Browser (ant-chrome) instead of a browser launched directly by OpenClaw.
Do not use this skill for generic browsing tasks that should stay inside OpenClaw's own browser runtime.
This skill assumes a same-host setup:
- OpenClaw Gateway and Ant Browser run on the same machine.
- Ant Browser LaunchServer is reachable on loopback.
- OpenClaw Browser has a preconfigured remote CDP profile pointing at the Ant Browser LaunchServer URL.
Read references/setup.md in this skill directory when the user is doing first-time setup, the browser profile is missing, or the launch endpoint cannot be reached.
Read references/http.md in this skill directory when you need exact request patterns for health checks, launch requests, runtime control, profile CRUD, automation script APIs, or log inspection.
Defaults
- Base URL:
ANT_CHROME_BASE_URL, default http://127.0.0.1:19876
- API header:
ANT_CHROME_API_HEADER, default X-Ant-Api-Key
- API key:
ANT_CHROME_API_KEY, optional
- Browser profile name: assume
ant-chrome unless the user tells you a different OpenClaw browser profile name
Workflow
- On Windows, prefer
scripts/invoke_ant_chrome_api.ps1 through pwsh or powershell for LaunchServer calls. On Unix-like hosts, use the curl patterns in references/http.md.
- Before any launch, stop, profile mutation, or automation-script run, verify LaunchServer with
GET /api/health from the host using exec.
- Choose the narrowest safe action:
- Check current unified CDP target:
GET /api/runtime/active
- Exact launch code:
GET /api/launch/{code}
- Selector or launch-code based runtime check:
POST /api/runtime/status
- Selector or launch-code based stop:
POST /api/runtime/stop
- Selector-based launch:
POST /api/launch
- Profile list/create/update/delete:
/api/profiles
- Automation script list/detail/run/runs:
