duoplus-agent

What This Skill Does

The duoplus-agent is a specialized automation interface designed to control DuoPlus cloud-based Android devices. It acts as a bridge between OpenClaw AI and the Android Debug Bridge (ADB), leveraging the StandardSoftwareService to perform complex mobile interactions. By sending Base64-encoded JSON payloads via broadcast intents, this skill allows for granular control over cloud-hosted phones, including coordinate-based clicking, text input, gesture navigation, and comprehensive UI state retrieval. It is designed to turn remote Android devices into fully programmable agents for testing, task automation, or remote research.

Installation

You can integrate this skill into your environment using the ClawHub CLI. Execute the following command in your terminal:

clawhub install openclaw/skills/skills/duoplusofficial/duoplus-agent

Ensure your development environment has ADB installed and that your workstation can communicate with the specific IP and port of your DuoPlus cloud device. Before execution, verify that the device is running the required StandardSoftwareService (version 2.0.0 or higher) by running the bundled script: scripts/check_env.sh <DEVICE_ID>.

Use Cases

• Automated Regression Testing: Execute repetitive user flows on Android apps by chaining clicks, swipes, and text inputs across different device configurations.
• Content Scraping: Use get_ui_state to extract text and component locations from dynamic mobile applications, allowing the AI to navigate complex login walls or multi-step forms.
• Cloud Phone Fleet Management: Maintain and monitor a cluster of Android cloud devices by remotely interacting with system settings or performing routine health checks through automated scripts.

Example Prompts

1. "Open the browser on my DuoPlus device, navigate to example.com, and take a screenshot of the landing page."
2. "Check the current screen state, find the login button, and perform a click at its coordinates."
3. "Type the password 'secure123' into the active text field and then swipe up to refresh the feed."

Tips & Limitations

• Asynchronous Flow: Most actions are 'fire-and-forget'. Always introduce a wait time of 1-3 seconds between an action and a follow-up get_ui_state request to allow the device's UI to update.
• Version Dependency: This skill is strictly tied to StandardSoftwareService. If a device has not been updated, or the service is not active, the broadcast receiver will fail silently.
• Error Handling: Since broadcast commands do not return action status, implement verification logic in your agent flows by comparing the UI state before and after your intended action. If the get_ui_state output does not reflect the expected change, include retry logic in your script.