> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Cloud agents quickstart

Create an environment and run a cloud agent from Warp in about 10 minutes, then inspect its commands and results.

Run one cloud-agent task from Warp in about 10 minutes. You’ll set up an environment if needed, send a request, and inspect the result. For a standing workflow with factory agents and automations, use the [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/) instead.

## Prerequisites

-   **Warp app** - Download from the [Warp download page](https://www.warp.dev/download).
-   **Warp account** - Create an account from the [Oz web app](https://oz.warp.dev)

Note

You need at least 20 credits available for this standalone workflow. See [cloud-agent access and billing](https://docs.warp.dev/platform/team-access-billing-and-identity/) for requirements.

* * *

## Running your first cloud agent

*About 10 minutes*

### 1\. Open Warp

Open the Warp app and sign in. This authenticates the cloud-agent setup flow with your Warp account.

### 2\. Run the `/cloud-agent` command

In Warp’s terminal input, type:

```bash
/cloud-agent
```

Warp checks for an environment and guides you through creating one if needed.

### 3\. Create your environment

An environment defines the agent’s workspace: a Docker image with your toolchain, repositories to check out, and commands to prepare them. It gives the agent the tools it needs even though it isn’t running on your laptop.

If you already have an environment, use it. To create another for a different project, run `/create-environment` in Warp.

For a new environment, provide:

-   **Name** - A label for this workspace.
-   **Repositories** - Enter `owner/repo` or select a repository. Click **Auth with GitHub** if you need to authorize access.
-   **Docker image** - Choose an image with your project’s tools, such as `python:3.11` or `node:20`, or click **Suggest image**.
-   **Setup commands** - Prepare dependencies with commands such as `pip install -r requirements.txt` or `npm ci`. Press `Enter` after each command.
-   **Description** - Optional notes for teammates using the environment.

See [configuring environments](https://docs.warp.dev/platform/environments/configuring-environments/) for detailed setup.

### 4\. Describe what you want the agent to do

Send a small, verifiable request, such as “Analyze test coverage and suggest one improvement. Do not change files.”

The agent works in the cloud environment: it checks out the configured repositories and runs the setup commands before working on your prompt. Watch its progress in Warp and send follow-up instructions when needed. Agents can run commands and change files in that workspace; review their work before using it.

### 5\. View run details

Inspect the commands, output, and any file changes to confirm the agent addressed your request:

-   In the Warp app, open the [conversations panel](https://docs.warp.dev/agents/local-agents/interacting-with-agents/#conversation-panel) to see all your agent runs.
-   Click the session link in your terminal output.
-   Go to the [Oz web app](https://oz.warp.dev) and navigate to the **Runs** tab.

The run record remains available after execution finishes. See [viewing cloud agent runs](https://docs.warp.dev/platform/viewing-cloud-agent-runs/) for sharing, steering, and continuing sessions, including from a browser or mobile device.

**Prefer using the CLI?** See the [Oz CLI quickstart](https://docs.warp.dev/agents/cli/oz-cli/quickstart/) for CLI-based workflows.

* * *

## Troubleshooting

-   **Environment setup fails** - See [environment troubleshooting](https://docs.warp.dev/platform/environments/troubleshooting-environments/) and [environment setup errors](https://docs.warp.dev/factories/api-and-sdk/troubleshooting/errors/environment-setup-failed/).
-   **Repository access fails** - See [GitHub authorization](https://docs.warp.dev/agents/cli/oz-cli/integration-setup/#how-github-authorization-works) and [authentication errors](https://docs.warp.dev/factories/api-and-sdk/troubleshooting/errors/external-authentication-required/).
-   **Usage is blocked** - See [access and billing requirements](https://docs.warp.dev/platform/team-access-billing-and-identity/) and [insufficient credits](https://docs.warp.dev/factories/api-and-sdk/troubleshooting/errors/insufficient-credits/).

## Next steps

-   [Cloud agents overview](https://docs.warp.dev/platform/) - Understand standalone runs and their configuration.
-   [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/) - Build a standing team workflow with agents and automations.
-   [Skills as agents](https://docs.warp.dev/platform/skills-as-agents/) - Make a request reusable, then use [scheduled agents](https://docs.warp.dev/platform/triggers/scheduled-agents-quickstart/) or [integrations](https://docs.warp.dev/platform/integrations/quickstart/) to trigger it.