DuoPlus cloud phone integration · macOS and Windows
Manage DuoPlus cloud phones in natural language
Ganhuo AI is a desktop client. Install it and enter your DuoPlus API key to get started. It supports bulk power on/off, app installation, command execution, and cloud-number SMS code lookups, with no command line required.
Already installed? See the connection steps
Type the following in Ganhuo AI and the client will show the key entry card.
Connect my cloud phones
- DUOPLUS API KEY
- dp-••••••••••••abcd
- Access region
- Chinese mainlandInternational
The API key is stored encrypted on your own machine. Enter it once and it stays valid.
Connection steps
- 01
Download and install the client
Available for macOS and Windows. Installation works like any other desktop application.
- 02
Generate a DuoPlus API key
In the DuoPlus console, go to Automation → API and generate an API key.
- 03
Enter the API key in the client
Open Ganhuo AI, type "Connect my cloud phones", then enter the API key and select an access region in the card that appears.
API keys are issued per team
A key covers the devices and data of the team it was generated under. To reach another team's devices, switch teams in the console and generate a new key.
The access region must match your account
There are two access regions — Chinese mainland and International — and accounts are not shared between them. Choosing the wrong one returns the error "invalid key", so check the region alongside the key itself.
Scope of functionality
- Device status and expiry lookup
- View the running status, expiry date, and renewal state of cloud phones in a given group.
- Bulk power and app management
- Power devices on or off and install or uninstall applications across multiple devices at once.
- Command execution and results
- Run commands on a device and receive screenshots or UI element data in return.
- Cloud-number SMS code lookup
- Retrieve SMS verification codes received by a linked cloud number.
Operational boundaries
Cloud phones host long-running account environments. The following four behaviours are fixed in the client.
- Device matching
- When a device name matches more than one device, the candidates are listed for you to confirm; none is selected automatically.
- Proxy channels
- Changing a proxy channel requires an explicit instruction from you and is never performed automatically.
- Billable actions
- Any action that incurs a charge is executed only after you confirm it in an authorisation card.
- Bulk results
- Bulk operations report a result per device, listing failed devices individually rather than reporting overall success.
Get started
Download the client, then follow the connection steps to enter your API key. Full details are in the integration guide.