Skip to content

Commit edcdac1

Browse files
rachaelrenkoz-agent
andcommitted
Standardize Oz web app procedures
Co-Authored-By: Oz <oz-agent@warp.dev>
1 parent 4ef4495 commit edcdac1

3 files changed

Lines changed: 32 additions & 22 deletions

File tree

158 KB
Loading
759 KB
Loading

src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx

Lines changed: 32 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -73,9 +73,9 @@ You can also search by title, prompt, or agent name, and add advanced filters fo
7373

7474
Click **New run** in the header to start a cloud agent.
7575

76-
1. **Select an agent (optional)** Choose **Quick run** to run as yourself, or choose a saved agent from the **Agent** dropdown.
77-
2. **Select an environment** — Choose which environment the agent runs in.
78-
3. **Add a prompt** — Provide context and instructions for this specific run.
76+
1. Select an agent, if needed. Choose **Quick run** to run as yourself, or choose a saved agent from the **Agent** dropdown.
77+
2. Select the environment where the agent should run.
78+
3. Add a prompt with context and instructions for this specific run.
7979

8080
**Quick run** runs as your own user. A saved agent uses its saved defaults, and your prompt adds context for this particular execution.
8181

@@ -109,11 +109,11 @@ Click any agent to view its details, then click **New run** to start a run from
109109

110110
### Creating a new agent
111111

112-
Click **New agent** to open the side pane.
112+
To create a saved agent:
113113

114-
1. **Click New agent** — Open the guided creation flow.
115-
2. **Define instructions and defaults** Add a name, description, prompt, optional skills, harness, model, environment, and secrets.
116-
3. **Click Create agent** — Save the agent so it appears on the Agents page and is available for future runs.
114+
1. Click **New agent** to open the guided creation flow.
115+
2. Define the instructions and defaults. Add a name, description, prompt, optional skills, harness, model, environment, and secrets.
116+
3. Click **Create agent**. The saved agent appears on the Agents page and is available for runs.
117117

118118
For deeper guidance on reusable skills and team-scoped identities, see [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) and [Agent identities](/agent-platform/cloud-agents/agents/).
119119

@@ -134,11 +134,17 @@ Click any skill to view its details, then click **New run** to start a run with
134134

135135
### Creating a skill for agents
136136

137-
Click **New agent** on the Skills page to open the skill creation flow.
137+
To create a skill for agents:
138138

139-
1. **Choose a repository** — Select a repository from an existing environment with GitHub access.
140-
2. **Define the skill** — Add a skill name, description, and instructions.
141-
3. **Open a Skill PR** — Create a pull request that adds the skill to the selected repository.
139+
1. Click **New agent** on the Skills page to open the skill creation flow.
140+
2. Choose a repository from an existing environment with GitHub access.
141+
3. Define the skill. Add a skill name, description, and instructions.
142+
4. Click **Open Skill PR** to create a pull request that adds the skill to the selected repository.
143+
144+
<figure>
145+
![Creating a skill for agents in the Oz web app.](../../../../assets/agent-platform/oz-web-app-new-skill.png)
146+
<figcaption>Creating a skill in the Oz web app.</figcaption>
147+
</figure>
142148

143149
After the PR is merged, refresh skills so the new skill appears in the Oz web app.
144150

@@ -159,13 +165,15 @@ Each schedule displays:
159165

160166
### Creating a schedule
161167

162-
Click **New schedule** in the header to create a scheduled agent.
168+
To create a scheduled agent:
163169

164-
1. **Name** — Give the schedule a descriptive name.
165-
2. **Frequency** — Set the cron schedule, with presets for common patterns.
166-
3. **Environment** — Select the environment to run in.
167-
4. **Agent (optional)** — Choose a saved agent to use.
168-
5. **Prompt** — Define what the agent should do each time it runs.
170+
1. Click **New schedule** in the header.
171+
2. Name the schedule. Use a descriptive name that explains what the scheduled agent does.
172+
3. Set the frequency. Choose a preset or enter a cron schedule.
173+
4. Select the environment where the scheduled agent should run.
174+
5. Choose a saved agent, if needed.
175+
6. Add the prompt that the agent should follow each time it runs.
176+
7. Click **Create schedule**. The schedule appears on the Schedules page.
169177

170178
### Managing schedules
171179

@@ -197,12 +205,14 @@ Each environment displays:
197205

198206
### Creating an environment
199207

200-
Click **New environment** in the header to create a new environment.
208+
To create a new environment:
201209

202-
1. **Name** — Give the environment a descriptive name.
203-
2. **Docker image** — Specify a Docker image. Warp provides prebuilt dev images, or you can use your own.
204-
3. **Repositories** — Add GitHub repos the agent should have access to.
205-
4. **Setup commands** — Define commands to run when the environment starts, such as `npm install`.
210+
1. Click **New environment** in the header.
211+
2. Name the environment. Use a descriptive name that explains the runtime context.
212+
3. Select the repositories the agent should be able to access.
213+
4. Choose a Docker image. Warp provides prebuilt dev images, or you can use your own.
214+
5. Add any setup commands that should run when the environment starts, such as `npm install`.
215+
6. Click **Create environment**. The environment appears on the Environments page.
206216

207217
:::note
208218
For advanced environment configuration, see [Environments](/agent-platform/cloud-agents/environments/) and the [CLI reference](/reference/cli/integration-setup/).

0 commit comments

Comments
 (0)