/adspower-browser

name: adspower-browser
description: "AdsPower profile operation via adspower-browser CLI. open/launch/start browser or profile, environment, config profile, AdsPower; create/update/delete/list profiles; groups, tags, proxies, dynamic proxy traffic; kernel download/list; client patch; API check-status. User phrases like open environment or map to commands such as open-browser."

AdsPower Local API with adspower-browser

The Skills CLI (npx adspower-browser) is the package manager for operate AdsPower browser profiles, groups, proxies, and application/category lists via the **adspower-browser** CLI. For more infomation about out product and services, visit [AdsPower Official Website](https://www.adspower.com/).

Install CLI

npm install -g adspower-browser

After installation, you can use any of these equivalent commands:

adspower-browser
adspower
ads

`adspower-browser` is the original command name. `adspower` and `ads` are aliases that point to the same CLI entry.

When to Use This Skill

Apply when the user:

• Asks to create, update, delete, or list AdsPower browser profiles
• Says 打开环境、配置文件、profile、AdsPower 等意指**启动已有**浏览器环境 → 使用 `open-browser`（CLI 或 MCP）；完整说法与工具映射见 [references/tool-intent-map.md](references/tool-intent-map.md)
• Mentions opening or closing browsers/profiles, fingerprint, UA, or proxy
• Wants to manage groups, tags, proxies, or check API status
• Refers to AdsPower or adspower-browser (and MCP is not running or not desired)

Ensure AdsPower is running (default port `50325`). Pass `--port` / `--api-key` when needed, or set the `ADS_API_KEY` environment variable before running `start`.

The CLI itself supports launching the AdsPower application via API key. If the AdsPower client is installed, AdsPower headless mode can also be launched via API key.

How to Run

The examples below use `ads` for brevity, but `adspower-browser` and `adspower` work the same way.

ads start -k <KEY>

If the `ADS_API_KEY` environment variable is set, you can start the CLI directly with:

ads start

General command form:

ads <command> [<arg>] [--port PORT] [--api-key KEY]

AdsPower client headless mode:

AdsPower Global：
Windows设备下： "AdsPower Global.exe" --headless=true --api-key=your_api_key --api-port=50325
MacOS设备下："/Applications/AdsPower Global.app/Contents/MacOS/AdsPower Global" --args --headless=true --api-key=your_api_key --api-port=50325
Linux设备下：adspower_global --headless=true --api-key=your_api_key --api-port=50325

**Two forms for `<arg>`:**

1. **Single value (shorthand)** — for profile-related commands, pass one profile ID or number:

• `ads open-browser <profile_id>`
• `ads close-browser <profile_id>`
• `ads get-profile-cookies <profile_id>`
• `ads get-browser-active <profile_id>`
• `ads get-profile-ua <profile_id>` (single ID; a numeric token is treated as `profile_no`)
• `ads new-fingerprint <profile_id>` (single ID; a numeric token is treated as `profile_no`)

2. **JSON string** — full parameters for any command (see Command Reference below):

• `ads open-browser '{"profile_id":"abc123","launch_args":"..."}'`
• Commands with no params: omit `<arg>` or use `'{}'`.

Essential Commands With AI Agents

You can use `ads -h` or `ads <command> -h` to view the specific parameters.

Start and stop CLI

ads start -k <KEY>                    # Start the adspower runtime
ads stop                              # Stop the adspower runtime
ads restart                           # Restart the adspower runtime
ads status                            # Get the status of the adspower runtime

Browser profile – open/close

ads open-browser <profile_id>                    # Or JSON: profile_id, profile_no?, ip_tab?, launch_args?, headless?, last_opened_tabs?, proxy_detection?, password_filling?, password_saving?, cdp_mask?, delete_cache?, device_scale?
ads close-browser <profile_id>                   # Or JSON: profile_id? | profile_no? (one required)

Browser profile – create/update/delete/list

ads create-browser '{"group_id":"0","user_proxy_config":{"proxy_soft":"no_proxy"},...}'  # group_id required: always include it; use "0" for Ungrouped; if given a group name, call get-group-list first; include either proxyid or user_proxy_config
ads update-browser '{"profile_id":"...",...}'    # profile_id required
ads delete-browser '{"profile_id":["..."]}'     # profile_id required
ads get-recycle-bin-list '{}'                   # page?, limit? (1-100). Omit either to use the Local API backend default. Last 30 days only
ads restore-recycle-bin '{"profile_id":["id1","id2"],"group_id":"123"}'  # profile_id[] or profile_no[], group_id required
ads get-browser-list '{}'                       # CLI defaults to page=1,limit=200 (Local API itself returns only 1). Or group_id?, limit?, page?, profile_id[]?, profile_no[]?, sort_type?, sort_order?, tag_ids?, tags_filter?, name?, name_filter?
ads get-opened-browser                          # No params

**Listing all environments:** `get-browser-list` returns `total_count` / `total_pages`. The CLI sends `page=1,limit=200` by default, so one call covers up to 200 profiles. If `total_pages > 1`, keep calling with the same filters and `page + 1` until every page is collected. For "operate on all environments in a group" tasks, gather all pages first, then act on every returned `profile_id` — never just the first.

Browser profile – move/cookies/UA/fingerprint/cache/share/active

ads move-browser '{"group_id":"1","user_ids":["..."]}'   # group_id + user_ids required
ads get-profile-cookies <profile_id>             # Or JSON: profile_id? | profile_no?
ads get-profile-ua <profile_id>                  # Or JSON: profile_id[]? | profile_no[]? (up to 10); numeric shorthand maps to profile_no[]
ads close-all-profiles                          # No params
ads new-fingerprint <profile_id>                 #