Quick Start

The dcd command line is intentionally designed to mimic the Maestro Cloud API. In most cases, you can just change maestro cloud to dcd cloud:

# maestro cloud --apiKey <apiKey> <appFile> <flowFile>

dcd cloud <appFile> <flowFile>

1. Install the CLI

The recommended install is the standalone binary — no Node required.

macOS / Linux

curl -fsSL https://get.devicecloud.dev/install.sh | sh

Windows

irm https://get.devicecloud.dev/install.ps1 | iex

npm

Install Node 22+, then run:

npm install -g @devicecloud.dev/dcd

2. Authenticate

Log in once in your browser — the CLI remembers your session, so you don't need to pass a key on every command:

dcd login

Running in CI or a headless environment? Use an API key instead. Find it in the console settings page and set it as an environment variable:

export DEVICE_CLOUD_API_KEY=your-api-key

See Authentication for more detail.

3. Run your first flow

iOS

dcd cloud <appFile>.app <flowFile>

Android

dcd cloud <appFile>.apk <flowFile>

That's it! Questions? Issues? Head to our Discord.

---

Upgrading the CLI

If you installed the standalone binary:

dcd upgrade

If you installed via npm:

npm install -g @devicecloud.dev/dcd@latest

Prerelease versions (not recommended): Occasionally, prerelease versions are available under the beta tag. See available versions on NPM.

npm install -g @devicecloud.dev/dcd@beta

For the standalone binary, set DCD_BETA=1 when you run the installer:

curl -fsSL https://get.devicecloud.dev/install.sh | DCD_BETA=1 sh

$env:DCD_BETA=1; irm https://get.devicecloud.dev/install.ps1 | iex

---

Limits

Every flow has a 10-minute execution limit. A flow that is still running when it reaches the limit is stopped and marked as failed, with a "Test run timed out after 10 minutes" error.

---

Next steps

• Flows & Workspaces — organise and run multiple flows

• Devices & OS Versions — choose Android API level or iOS version

• App Management — upload and reuse binaries

• CI/CD Integration — run tests in your pipeline