> ## Documentation Index
> Fetch the complete documentation index at: https://developer.watson-orchestrate.ibm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Installing watsonx Orchestrate Developer Edition

You can install or uninstall watsonx Orchestrate Developer Edition using ADK CLI commands. To get started, make sure Docker Engine is installed and the .env file is properly configured.

```mermaid theme={null}
 graph LR
    Container[Configure Docker Engine] --> ENV[Configure .env file]
    ENV --> Server[Install or uninstall Developer Edition] 
```

## Installation prerequisites

Before installing watsonx Orchestrate Developer Edition, make sure you meet the following requirements:

<AccordionGroup>
  <Accordion title="Hardware requirements">
    Your computer needs to meet the following requirements:

    | Component | Minimum | Recommended |
    | --------- | ------- | ----------- |
    | CPU       | 8-core  | 8-core      |
    | RAM       | 16 GB   | 32 GB       |
  </Accordion>

  <Accordion title="watsonx services">
    You must have access to at least one of the following services:

    * watsonx Orchestrate
    * watsonx.ai
  </Accordion>

  <Accordion title="watsonx Orchestrate Developer Edition license">
    You need a valid license for watsonx Orchestrate Developer Edition. You can obtain a license by:

    * Purchasing a SaaS license for watsonx Orchestrate
    * Contacting IBM Sales for a direct purchase
  </Accordion>
</AccordionGroup>

## Configuring container manager

You install and uninstall watsonx Orchestrate Developer Edition automatically using ADK CLI commands. Since the installation runs inside a Docker container, you need to have Docker Engine and Docker Compose installed on your machine.

You can install Docker Engine and Docker Compose natively on systems that offer official support. Alternatively, for systems without native support, you can use container managers such as Rancher or Colima to install and configure them.

Click the tabs below to learn how to install and configure Docker Engine and Docker Compose based on your operating system.

<Tabs>
  <Tab title="macOS">
    macOS doesn’t officially support Docker Engine or Docker Compose. To install and run them, use a container manager like Rancher or Colima.

    * To install Docker Engine and Docker Compose using Rancher, see see [Rancher Desktop for macOS](https://docs.rancherdesktop.io/getting-started/installation/#macos).
      * Then, configure Rancher using the settings described in [Rancher settings](https://github.com/IBM/ibm-watsonx-orchestrate-adk/blob/main/_docs/recommended-docker-settings/rancher-settings.md).
          <Note>
            If you use Apple Silicon hardware with Rancher Desktop, enable Rosetta support to use the Apple Virtualization (VZ) framework.
          </Note>
    * To install Docker Engine and Docker Compose using Colima, see [Colima](https://github.com/abiosoft/colima?tab=readme-ov-file#installation).
      * Then, configure Colima using the settings described in [Colima settings](https://github.com/IBM/ibm-watsonx-orchestrate-adk/blob/main/_docs/recommended-docker-settings/coilma-settings.md).
  </Tab>

  <Tab title="Windows">
    On Windows, you can install Docker Engine and Docker Compose using Windows Subsystem for Linux (WSL). Alternatively, you can use a container manager like Rancher to simplify setup and manage containers more efficiently.

    * To install Docker Engine and Docker Compose using Rancher, see [Rancher Desktop for Windows](https://docs.rancherdesktop.io/getting-started/installation/#windows).
    * To install Docker Engine and Docker Compose using WSL, see:
      1. [How to install Linux on Windows with WSL](https://learn.microsoft.com/en-us/windows/wsl/install)
      2. [Install Docker Engine](https://docs.docker.com/engine/install/)
      3. [Overview of installing Docker Compose](https://docs.docker.com/compose/install/)

             <Note>
               **Note:**

               * WSL 2 with Ubuntu distribution is recommended.
               * Install [Docker Compose v2](https://docs.docker.com/compose/releases/migrate/). The ADK is not compatible with Compose v1.
               * To ensure better integration and performance, install the ADK inside your WSL environment, as your server will be running there. Once installed, you can build and manage your agents directly within WSL for a smoother development experience.
             </Note>
  </Tab>

  <Tab title="Linux">
    Linux-based systems officially support Docker Engine and Docker Compose, so you can install them directly. If you prefer, you can use a container manager such as Rancher or Colima to help set up and manage your container environment.

    * To install Docker Engine and Docker Compose using Rancher, see [Rancher Desktop for Linux](https://docs.rancherdesktop.io/getting-started/installation/#linux).
    * To install Docker Engine and Docker Compose using Colima, see [Colima](https://github.com/abiosoft/colima?tab=readme-ov-file#installation).
    * To install Docker Engine and Docker Compose directly, see:
      1. [Install Docker Engine](https://docs.docker.com/engine/install/)
      2. [Overview of installing Docker Compose](https://docs.docker.com/compose/install/)
             <Note>
               **Note:**
               Install [Docker Compose v2](https://docs.docker.com/compose/releases/migrate/). The ADK is not compatible with Compose v1.
             </Note>
  </Tab>
</Tabs>

After you install Docker Engine and Docker Compose, open your terminal, Command Prompt (CMD), or PowerShell and run the `docker` and `docker compose` commands. These commands display a list of available options and subcommands that you can use to interact with Docker.

The image below shows an example of the output returned by these commands.

<Frame>
  <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/docker_commands.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=b1d8a59885053ae140f85504050196d2" width="1583" height="530" data-path="assets/developer_edition/install/docker_commands.png" />
</Frame>

## Configuring .env file

The `.env` file is a plain text file that stores environment variables. The ADK uses the variables you define in this file to authenticate your user and install watsonx Orchestrate Developer Edition.

The variables you need to configure depend on the authentication method you choose. You can authenticate using one of the following methods:

* **watsonx Orchestrate account**

  Use this method if you have a watsonx Orchestrate account or if you're using a 30-day trial.

* **myIBM**

  Use this method if you purchased a watsonx Orchestrate Developer Edition license through sales or if you're using an on-premises version.

* **Custom Image Registry**

  Use this method if you’ve already copied the required Docker images to an image registry. For example, an Artifactory repository.

Click the tabs below to view instructions for configuring the `.env` file based on your authentication method.

<Tabs>
  <Tab title="watsonx Orchestrate account">
    To authenteticate using watsonx Orchestrate account:

    <Steps>
      <Step title="Create a .env file">
        Create a file named `.env`.
      </Step>

      <Step title="Configure the .env file">
        Add the following variables to your `.env` file:

        <ParamField path="WO_DEVELOPER_EDITION_SOURCE">
          The source ID for the watsonx Orchestrate Developer Edition. Set `orchestrate`.
        </ParamField>

        <ParamField path="WO_INSTANCE">
          The watsonx Orchestrate service instance URL.

          To obtain the service instance URL, follow these steps:

          1. [Log in](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/current?topic=orchestrate-logging-in-watsonx) to your watsonx Orchestrate account.

          2. Click your user profile and open the **Settings** page.

                       <Frame>
                         <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/click_settings.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=f17dafdccac87e72826df5e1d657ac38" width="285" height="472" data-path="assets/developer_edition/install/click_settings.png" />
                       </Frame>

          3. Open the **API details** tab.

          4. Copy your service instance URL.

                       <Frame>
                         <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/get_instance_url.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=80a79e43feea9bc84f79915e89a6fdb0" width="827" height="447" data-path="assets/developer_edition/install/get_instance_url.png" />
                       </Frame>
        </ParamField>

        <ParamField path="WO_API_KEY">
          The watsonx Orchestrate API key.

          To obtain the API key, follow these steps:

          1. [Log in](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/current?topic=orchestrate-logging-in-watsonx) to your watsonx Orchestrate account.

          2. Click your user profile and open the **Settings** page.

                       <Frame>
                         <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/click_settings.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=f17dafdccac87e72826df5e1d657ac38" width="285" height="472" data-path="assets/developer_edition/install/click_settings.png" />
                       </Frame>

          3. Open the **API details** tab.

          4. Click **Generate API key**.

                       <Frame>
                         <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/get_api_key.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=787b0bb386ff278c31ee19cb57115f4a" width="827" height="447" data-path="assets/developer_edition/install/get_api_key.png" />
                       </Frame>

                       <Warning>
                         Your API key is unique and can't be edited or deleted in the settings page. You must save the API key in a safe location.
                       </Warning>
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          WO_DEVELOPER_EDITION_SOURCE=orchestrate
          WO_INSTANCE=<service_instance_url>
          WO_API_KEY=<wxo_api_key>
          ```
        </Expandable>

        If you're using an on-premises setup, you also need to set the following environment variables:

        <ParamField path="DOCKER_IMAGE_PULL_LAYERS_PARALLELISM">
          Boolean environment variable that controls whether image layers are pulled in parallel. Defaults to `true`.

          Treated as `false` if `DOCKER_IMAGE_PULL_PARALLEL_WORKERS_COUNT` is set to `1`.
        </ParamField>

        <ParamField path="DOCKER_IMAGE_PULL_PARALLEL_WORKERS_COUNT">
          Integer value that defines how many Docker image layers are pulled in parallel. Accepts values from `1` to `10`.

          Values outside this range trigger a fallback to the default value. Defaults to `7`.
        </ParamField>

        <ParamField path="USE_RANGE_REQUESTS_IN_DOCKER_IMAGE_PULLS">
          Boolean environment variable that enables ranged requests when pulling large layers. Defaults to `true`.

          <Note>
            **Note:**

            Only takes effect when `DOCKER_IMAGE_PULL_LAYERS_PARALLELISM` is enabled.
          </Note>
        </ParamField>

        <ParamField path="WO_VERIFY_SSL">
          For on-premises (CPD) deployments, ADK uses SSL authentication by default to connect to a registry proxy in your watsonx Orchestrate on-premises environment. You can control this behavior by setting the WO\_VERIFY\_SSL environment variable. Use this variable to enable or disable SSL authentication.

          <Tabs>
            <Tab title="Enable with the system SSL certificate">
              To enable SSL security using the system’s default SSL certificate, set the `WO_VERIFY_SSL` environment variable to `True`:

              ```txt .env theme={null}
              WO_VERIFY_SSL=True
              ```
            </Tab>

            <Tab title="Enable with a custom SSL certificate">
              To use a custom SSL certificate, set the `WO_VERIFY_SSL` variable to the path of your certificate:

              ```txt .env theme={null}
              WO_VERIFY_SSL=<path-to-SSL-certificate>
              ```
            </Tab>

            <Tab title="Disable SSL Security">
              To disable SSL authentication, set the `WO_VERIFY_SSL` environment variable to `False`:

              ```txt .env theme={null}
              WO_VERIFY_SSL=False
              ```
            </Tab>
          </Tabs>
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          DOCKER_IMAGE_PULL_LAYERS_PARALLELISM=true
          DOCKER_IMAGE_PULL_PARALLEL_WORKERS_COUNT=7
          USE_RANGE_REQUESTS_IN_DOCKER_IMAGE_PULLS=true
          WO_VERIFY_SSL=True
          ```
        </Expandable>

        Additionally, if you operate in a region other than us-south, configure the region variables. Set the following variables:

        <ParamField path="ASSISTANT_LLM_API_BASE">
          The assistant LMM API endpoint for your region
        </ParamField>

        <ParamField path="ASSISTANT_EMBEDDINGS_API_BASE">
          The assistant embedding API endpoint for your region.
        </ParamField>

        <ParamField path="ROUTING_LLM_API_BASE">
          The routing LLM API endpoint for your region.
        </ParamField>

        <ParamField path="WATSONX_URL">
          The watsonx endpoint for your region.
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          ASSISTANT_LLM_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          ASSISTANT_EMBEDDINGS_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          ROUTING_LLM_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          WATSONX_URL=https://<region-code>.ml.cloud.ibm.com/
          ```

          **Where:**

          * `<region-code>`: refers to the region code for your location. For example: `eu-de`
        </Expandable>
      </Step>
    </Steps>
  </Tab>

  <Tab title="myIBM">
    To authenteticate using myIBM:

    <Steps>
      <Step title="Create a .env file">
        Create a file named `.env`.
      </Step>

      <Step title="Configure the .env file">
        Add the following variables to your `.env` file:

        <ParamField path="WO_DEVELOPER_EDITION_SOURCE">
          The source ID for the watsonx Orchestrate Developer Edition. Set `myibm`.
        </ParamField>

        <ParamField path="WO_ENTITLEMENT_KEY">
          An entitlement key from a valid watsonx.ai instance.

          To obtain the entitlement key, follow these steps:

          1. Access [My IBM](https://myibm.ibm.com/).

          2. Click **View Library**.

                       <Frame>
                         <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/view_library.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=d09ebda0ac33e617aaad386edb6b7b79" width="1199" height="479" data-path="assets/developer_edition/install/view_library.png" />
                       </Frame>

          3. Click **Add a new key +**.

                       <Frame>
                         <img src="https://mintcdn.com/ibm-2e3153bf/CUC4--rm2jCi7sPV/assets/developer_edition/install/new_key.png?fit=max&auto=format&n=CUC4--rm2jCi7sPV&q=85&s=147b63d4f57f61fa34ab5350d247e546" width="1564" height="427" data-path="assets/developer_edition/install/new_key.png" />
                       </Frame>

          4. Copy the entitlement key.
        </ParamField>

        <ParamField path="WATSONX_APIKEY">
          The API key of your instance. To get your API Key, see [Managing API Keys](https://cloud.ibm.com/docs/account?topic=account-userapikey\&interface=ui#create_user_key).
        </ParamField>

        <ParamField path="WATSONX_SPACE_ID">
          A watsonx.ai instance on IBM Cloud. This instance is required to setting up the Deployment Space for the watsonx Orchestrate Developer Edition. If you don’t have one, create it and locate your `space ID`. You can create a new instance and get the `space ID` in the [Developer access](https://dataplatform.cloud.ibm.com/developer-access?context=wx) page on IBM Cloud.
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          WO_DEVELOPER_EDITION_SOURCE=myibm
          WO_ENTITLEMENT_KEY=<my_entitlement_key>
          WATSONX_APIKEY=<my_watsonx_api_key>
          WATSONX_SPACE_ID=<my_space_id>
          ```
        </Expandable>

        Additionally, if you operate in a region other than us-south, configure the region variables. Set the following variables:

        <ParamField path="ASSISTANT_LLM_API_BASE">
          The assistant LMM API endpoint for your region
        </ParamField>

        <ParamField path="ASSISTANT_EMBEDDINGS_API_BASE">
          The assistant embedding API endpoint for your region.
        </ParamField>

        <ParamField path="ROUTING_LLM_API_BASE">
          The routing LLM API endpoint for your region.
        </ParamField>

        <ParamField path="WATSONX_URL">
          The watsonx endpoint for your region.
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          ASSISTANT_LLM_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          ASSISTANT_EMBEDDINGS_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          ROUTING_LLM_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          WATSONX_URL=https://<region-code>.ml.cloud.ibm.com/
          ```

          **Where:**

          * `<region-code>`: refers to the region code for your location. For example: `eu-de`
        </Expandable>
      </Step>
    </Steps>
  </Tab>

  <Tab title="Custom Image Registry">
    To authenteticate using a custom image registry:

    <Steps>
      <Step title="Create a .env file">
        Create a file named `.env`.
      </Step>

      <Step title="Configure the .env file">
        Add the following variables to your `.env` file:

        <ParamField path="WO_DEVELOPER_EDITION_SOURCE">
          The source ID for the watsonx Orchestrate Developer Edition. Set `custom`.
        </ParamField>

        <ParamField path="REGISTRY_URL">
          The URL of the image registry that hosts the watsonx Orchestrate Developer Edition images.
        </ParamField>

        <ParamField path="REGISTRY_USERNAME">
          The username for authenticating with the image registry. Leave it blank to skip login.
        </ParamField>

        <ParamField path="WATSONX_SPACE_ID">
          The password for authenticating with the image registry. Leave it blank to skip login.
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          WO_DEVELOPER_EDITION_SOURCE=custom
          REGISTRY_URL=<registry_url>
          REGISTRY_USERNAME=<registry_username>
          REGISTRY_PASSWORD=<registry_password>
          ```
        </Expandable>

        Additionally, if you operate in a region other than us-south, configure the region variables. Set the following variables:

        <ParamField path="ASSISTANT_LLM_API_BASE">
          The assistant LMM API endpoint for your region
        </ParamField>

        <ParamField path="ASSISTANT_EMBEDDINGS_API_BASE">
          The assistant embedding API endpoint for your region.
        </ParamField>

        <ParamField path="ROUTING_LLM_API_BASE">
          The routing LLM API endpoint for your region.
        </ParamField>

        <ParamField path="WATSONX_URL">
          The watsonx endpoint for your region.
        </ParamField>

        <Expandable title=".env example">
          ```txt .env theme={null}
          ASSISTANT_LLM_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          ASSISTANT_EMBEDDINGS_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          ROUTING_LLM_API_BASE=https://<region-code>.ml.cloud.ibm.com/
          WATSONX_URL=https://<region-code>.ml.cloud.ibm.com/
          ```

          **Where:**

          * `<region-code>`: refers to the region code for your location. For example: `eu-de`
        </Expandable>
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Optional: Configuring caching layers for on-premises

If you use a watsonx Orchestrate on-premises instance to pull images, you can configure caching layers to speed up Docker image downloads. This setup creates a cache in the ADK watsonx Orchestrate folder and stores all pulled layers. With caching enabled, each layer downloads only once during the cache period, which you control. You can reuse these layers whenever needed. All cached layers appear in the folder located at `<home>/.cache/orchestrate`.

To configure caching layers, add the following environment variable to your `.env` file:

<ParamField path="IGNORE_DOCKER_LAYER_CACHING">
  Boolean environment variable that determines whether CPD Docker image layers are cached in the local orchestrate cache during pulls. Defaults to `false`.
</ParamField>

<Expandable title=".env example">
  ```txt .env theme={null}
  IGNORE_DOCKER_LAYER_CACHING=false
  ```
</Expandable>

<Note>
  To clean up cached image layers, use the ADK CLI. For more information, see [Cleaning on-premises cache layers](./manage_local_server#cleaning-on-premises-cache-layers).
</Note>

## Installing watsonx Orchestrate Developer Edition components

Use the `orchestrate <component> start` command to install watsonx Orchestrate Developer Edition components.

Before you begin, ensure the following prerequisites are met:

* [Docker Engine and Docker Compose are installed](#configuring-container-manager)
* [A valid .env file is configured](#configuring-env-file)

This command pulls the required images and creates Docker containers for the selected components. You can install the following:

* [watsonx Orchestrate Developer Edition: watsonx Orchestrate server](#installing-watsonx-orchestrate-developer-edition%3A-watsonx-orchestrate-server)
* [watsonx Orchestrate Developer Edition: Orchestrate copilot server](#installing-watsonx-orchestrate-developer-edition%3A-orchestrate-copilot-server)

<Note>
  **Note:**

  * If you encounter issues during installation, see the [Troubleshooting](../release/troubleshooting) section.
  * After pulling the images, you can set the WO\_DEVELOPER\_EDITION\_SKIP\_LOGIN environment variable to true to skip ICR login. The CLI uses existing images without downloading new ones.
</Note>

### Installing watsonx Orchestrate Developer Edition: watsonx Orchestrate server

The watsonx Orchestrate server runs locally on your machine. You can use it to gain more control when developing and debugging your agents.

To install watsonx Orchestrate server, run:

```bash BASH theme={null}
orchestrate server start -e <path-.env-file>
```

<Expandable title="command flags">
  <ResponseField name="--env-file / -e" type="string" required={true}>
    Path to your `.env` file.
  </ResponseField>

  <ResponseField name="--with-langfuse / -l" type="boolean">
    Enable Langfuse support.
  </ResponseField>

  <ResponseField name="--with-ibm-telemetry / -i" type="boolean">
    Enable IBM's native observability framework.
  </ResponseField>

  <ResponseField name="--accept-terms-and-conditions" type="boolean">
    Accept the terms and conditions shown in the logs when the server starts.
  </ResponseField>

  <ResponseField name="--with-doc-processing / -d" type="boolean">
    Enable IBM Document Processing to extract information from business documents. This activates the Watson Document Understanding service.
  </ResponseField>

  <ResponseField name="--with-voice" type="boolean">
    Enable voice support.
  </ResponseField>

  <ResponseField name="--with-langflow" type="boolean">
    Enable Langflow support. For more information about Langflow, see [Authoring Langflow tools](../langflow/overview).
  </ResponseField>

  <ResponseField name="--cert-bundle-path" type="string" required={false}>
    Path to a custom certificate bundle file.
  </ResponseField>
</Expandable>

Once installed, the following services become available:

* **OpenAPI Docs**: `http://localhost:4321/docs`. This API documentation is also available in the [watsonx Orchestrate Developer Edition APIs](../apis/agent-release-environments/create-an-environment-for-an-agent).
* **API Base URL**: `http://localhost:4321/api/v1`

<Note>
  **Note:**
  This command doesn’t start the local UI for watsonx Orchestrate. To start it, run `orchestrate chat start`. For more information, see [Launching the local UI](./manage_local_server#launching-the-local-ui).
</Note>

You can also use a custom `docker-compose.yml` file to install watsonx Orchestrate server. However, **ADK does not officially support custom configurations. Make sure you understand the changes before proceeding**. For more information, see [Using custom watsonx Orchestrate Developer Edition docker file](./custom_yaml).

### Installing watsonx Orchestrate Developer Edition: Orchestrate copilot server

The Orchestrate copilot server enables the copilot assistant, which helps you build agents and tools through the CLI chat.

To install Orchestrate copilot server, run:

```bash BASH theme={null}
orchestrate copilot start --env-file <env_file>
```

<Expandable title="command flags">
  | Flag                | Type   | Required | Description                                                                      |
  | ------------------- | ------ | -------- | -------------------------------------------------------------------------------- |
  | `--env-file` (`-e`) | string | Yes      | The path to an env file containing configuration options for the Copilot server. |
</Expandable>

## Stopping watsonx Orchestrate Developer Edition components

Use the `orchestrate <component> stop` command to stop a watsonx Orchestrate Developer Edition components.

<Note>
  **Note:**
  After stopping a component, run the installation command again to restart it.
</Note>

### Stopping watsonx Orchestrate Developer Edition: watsonx Orchestrate server

To stop watsonx Orchestrate server, run:

```bash BASH theme={null}
orchestrate server stop
```

### Stopping watsonx Orchestrate Developer Edition: Orchestrate copilot server

To stop Orchestrate copilot server, run:

```bash BASH theme={null}
orchestrate copilot stop
```

## Uninstalling watsonx Orchestrate Developer Edition components

To uninstall all watsonx Orchestrate Developer Edition components, reset the server and then remove the containers using Docker.

<Steps>
  <Step title="Reset the server">
    Run the following command to reset the server:

    ```bash BASH theme={null}
    orchestrate server reset
    ```
  </Step>

  <Step title="Delete all containers and volumes">
    Run the following command to remove all containers and volumes:

    ```bash BASH theme={null}
    docker system prune -a --volumes
    ```
  </Step>
</Steps>

## What's Next?

After installing watsonx Orchestrate Developer Edition, you can use server commands in the ADK CLI to interact with the platform. For more details, see the ADK CLI documentation.

* [watsonx Orchestrate Developer Edition: watsonx Orchestrate server commands](./manage_local_server)
* [watsonx Orchestrate Developer Edition: Orchestrate copilot server commands](../_releases/1.15.0/copilot/creating_agent)

You can also use the watsonx Orchestrate Developer Edition APIs to support agent development and testing. For more information, see [watsonx Orchestrate Developer Edition APIs](../apis/orchestrate-agent/chat-with-orchestrate-assistant-as-stream).