Windows Node and Android Node are in testing. They are available to try, but compatibility and reliability are still being validated. An available installer does not mean every system, phone model or operation has been verified.
Wait for the task you already submitted
A build may take a minute while the agent's request waits only four seconds. The October 13 Connector 0.1.3 release adds a common bounded wait across CLI, MCP and SDK: return the result if it is ready, otherwise return the current state and existing jobId so the caller can follow the same task.
task.wait accepts waitMs from 0 to 30000 milliseconds, defaulting to 4000. Zero reads the current state immediately. queued or running is not proof of failure. Save the jobId and wait again; closing the client or reaching the wait limit does not cancel device work. Explicit cancellation uses task.cancel and remains cooperative.
Follow-up reads need the same account and grant plus task read permission. Existing grants are not expanded automatically. If waiting is denied, check the grant instead of resubmitting the command. The optional executionTimeoutMs is a separate total budget, including queue time; later waits and lease renewals never reset it.
Replace JOB_ID below with the identifier returned by your invocation. Both commands read the existing task. Treat success as a terminal result with the expected output, not merely a successful HTTP response or an expired wait.
adc task wait JOB_ID --wait 4000 --json
adc invoke task.wait --args '{"jobId":"JOB_ID","waitMs":4000}' --jsonConnect through the official domain
The official hosted service uses https://adc.zioon.tech. Use this origin for new setup and agent login. Self-hosted installations continue to use their own HTTPS origin and share the same authorization, approval and local execution model. Hosting location does not change where a device tool runs.
Upgrade an existing installation with adc update, then inspect adc-node status for the version and connection state. Normal updates preserve device identity. Changing service origin or replacing an expired credential is a different operation; check local status and the troubleshooting guide before unpairing.
The new execution budget field requires an updated Connector; older strict protocol readers may reject it. Keep requests unchanged until the target has been updated. After upgrading, verify a read-only call through the access your agent actually uses.
adc update --check
adc update
adc-node statusChoose the installation for your device
Devices → Pair device offers macOS, glibc Linux, Windows x64 and Android installation paths. Desktop installers include a runtime. Android uses an APK and the service URL and pairing code from the console; its screen capture and UI actions require permissions granted locally on the phone.
Windows Node and Android Node remain in testing. The current Android package uses development signing and manual installation and updates. Testing on Xiaomi/MIUI does not certify every Android model. Android exposes mobile tools rather than the desktop filesystem and shell toolset; check the target's advertised capabilities.