From 62a0c75f31798a66c1c9813aeb009473e301dcac Mon Sep 17 00:00:00 2001 From: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Date: Thu, 25 Jun 2026 12:03:12 -0600 Subject: [PATCH] docs(environments): add Oz web app creation method, reorder to web app > guided setup > CLI MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The environments article had a screenshot of the Oz web app 'Create environment' panel with no accompanying instructions — the flow was undocumented. Changes: - Add 'Create an environment from the Oz web app' section with 4-step procedure (name + repos + Docker image → optional fields → Create environment) - Note the 'Easy Setup in Warp' button that links to the guided setup flow - Reorder creation methods: Oz web app → guided setup in Warp → CLI - Move the existing screenshot under the new web app section - Fix screenshot caption: 'Creating a new environment' → 'The Create environment panel' - Update intro sentence to describe all three methods upfront Discovered while reviewing the environments page linked from PR #236 (software factory guides). The existing screenshot was placed before the guided setup section, implying it documented that flow — but it showed the Oz web app UI, which has its own distinct creation form. Co-Authored-By: Oz --- .../cloud-agents/environments.mdx | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/src/content/docs/agent-platform/cloud-agents/environments.mdx b/src/content/docs/agent-platform/cloud-agents/environments.mdx index b4271395..aace3166 100644 --- a/src/content/docs/agent-platform/cloud-agents/environments.mdx +++ b/src/content/docs/agent-platform/cloud-agents/environments.mdx @@ -128,7 +128,7 @@ The fix the agent applies matches what runs in CI and what your teammates see wh ### Where to configure environments -You can create and configure environments with Warp’s guided setup, or through the CLI. Use the guided flow when you’re first getting started, and use the CLI when you want full control or need to automate environment creation. +You can create environments in three ways: from the Oz web app, using the guided setup in Warp, or through the CLI. **Before you begin** @@ -146,14 +146,25 @@ Musl-based Docker images (such as Alpine Linux) are not supported. The agent run Create one environment per codebase, then reuse it across triggers like Slack, Linear, and CLI runs. ::: +### Create an environment from the Oz web app +
![Creating a new environment in the Oz Web App.](../../../../assets/agent-platform/oz-web-app-new-environment.png) -
Creating a new environment in the Oz web app.
+
The Create environment panel in the Oz web app.
-### Create an environment with guided setup (recommended) +1. Open the [Environments page in the Oz web app](https://oz.warp.dev/environments) and click **New environment**. +2. Enter a name, select one or more repositories, and enter a **Docker image reference**. Click **Suggest** to have Oz recommend an image based on your repos, or start from one of [Warp's prebuilt dev images](https://github.com/warpdotdev/oz-dev-environments). +3. Optionally, add setup commands, configure cloud provider access (AWS or GCP), or add a description. +4. Click **Create environment**. + +:::tip +The **Easy Setup in Warp** button at the bottom of the form opens the guided setup in the Warp desktop app, which inspects your repos and suggests configuration automatically. +::: + +### Create an environment with guided setup in Warp -Use [`/create-environment`](warp://action/create_environment) when you want Warp to inspect your repos and recommend an environment configuration automatically. This is the fastest way to get started: Warp detects your languages, frameworks, and tools, then suggests appropriate images and setup commands. +Use [`/create-environment`](warp://action/create_environment) when you want Warp to inspect your repos and recommend an environment configuration automatically. Warp detects your languages, frameworks, and tools, then suggests appropriate images and setup commands. You can run the command inside a Git repo directory with no argument, or with one or more repo paths or URLs.