Skip to content

Agents > Oz Cloud Agents & Orchestration

Oz web app for cloud agents

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Use the Oz web app to manage cloud agents, view runs, create schedules, and configure environments and integrations from any browser or mobile device.

The Oz web app provides a visual interface for managing cloud agents. You can start runs, browse agents and skills, create schedules, configure environments, and set up integrations—all without installing Warp or using the CLI.

Watch this short demo to create an environment and run an agent using the Oz web app:

PagePathWhat you can do
Runs/runsView all runs, filter by status/source/creator, start new runs, inspect transcripts
Agents/agentsBrowse saved agents, create agents, configure defaults, and start runs
Skills/skillsBrowse skills from your environments, view suggested skills, create skills for agents, and start runs
Schedules/schedulesCreate scheduled agents, pause/enable schedules, view run history
Environments/environmentsCreate and manage environments with repos, Docker images, and setup commands
Secrets/secretsCreate and manage Warp-managed secrets for cloud agent runs
Integrations/integrationsConnect Slack and Linear to trigger agents from external tools

The Oz web app's management view.

The Oz web app management view.

The Oz web app is ideal when you want to:

  • Monitor agent activity — View runs, check status, and inspect outputs from any device
  • Start quick runs — Dispatch agents without opening a terminal
  • Manage agents and skills — Create saved agents, browse skills from connected repositories, and start runs from either configuration
  • Manage schedules visually — Create and edit scheduled agents with a guided interface
  • Configure environments — Set up repos, Docker images, and setup commands through a form-based flow
  • Set up integrations — Connect Slack and Linear with a guided setup flow

For scripting, automation, and CI/CD workflows, use the Oz CLI or API.

When you first sign in to the Oz web app, you’ll see a guided onboarding flow that helps you get started based on your goals.

The onboarding asks “What brings you to Oz?” and offers three paths:

  • Create an agent automation — Walks you through setting up a scheduled agent, integration-triggered agent, or other automation
  • Run Cloud Agents in Warp — Opens the Warp desktop app (or takes you to the download page) to run cloud agents interactively
  • Build an app that uses agents — Links to the Oz Platform docs for using the CLI, SDK, or API

You can skip onboarding at any time to go directly to the Runs page.

The Runs page (/runs) is your central view for monitoring cloud agent activity. It shows runs across your account and team, where applicable, including those triggered from the CLI, API, integrations, and schedules.

Each run displays the following information:

FieldDescription
StatusWorking, succeeded, failed, canceled, errored, or blocked
TitleThe run’s title or prompt summary
EnvironmentWhich environment the agent ran in
CreatorWho started the run
SourceWhere the run was triggered from (CLI, API, Slack, Linear, scheduled)
ArtifactsAny outputs like PRs or files created
CreditsHow many credits the run consumed

Click any run to open the detail pane, where you can view the full transcript, artifacts, and metadata.

Quick filterShows
AllAll runs
MineOnly runs you created
ActiveRuns currently in progress
FailedRuns that failed
RecurringRuns triggered by schedules

You can also search by title, prompt, or agent name, and add advanced filters for source, status, creator, and date range.

To start a new run:

  1. Click New run in the header to start a cloud agent.
  2. Select an agent, if needed. Choose Quick run to run as yourself, or choose a saved agent from the Agent dropdown.
  3. Select the environment where the agent should run.
  4. Add a prompt with context and instructions for this specific run.

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

The Oz web app renders multi-agent orchestrations as nested rows on the Runs page, so you can follow parent and child execution together.

Open a parent run from the Runs page. When the run has children, the detail pane adds a Sub-agents tab next to Details:

  • Each child agent row shows the child’s current status and title. Click a row to open that child’s detail pane; closing it returns you to the parent’s Sub-agents tab.
  • The parent’s own status badge at the top of the detail pane reflects the parent’s work, not its children. Open a child to inspect its state directly.

The Agents page (/agents) is where you browse, create, and run saved agents. Agents are reusable cloud agent configurations that can include a prompt, skills, harness, model, environment, and secrets.

Skills are reusable instruction sets stored in repositories. You can attach existing skills to an agent through the Skills field; for more details, see Skills as Agents.

Saved agents use Warp’s team-scoped identity model, which lets a reusable agent own runs and carry default configuration for teammates. You manage saved agents from the Agents page. For plan limits, API endpoints, and API key binding behavior, see Agent identities.

The Agents page in the Oz web app.

The Agents page in the Oz web app.

Open an agent to review its prompt, skills, harness, model, environment, and attached secrets. From the detail pane, you can inspect activity, create schedules, edit configuration, or start a run from the saved agent.

Click any agent to view its details, then click New run to start a run from that saved configuration. You can also click New run from the header to start a run with optional agent selection.

To create a saved agent:

  1. Click New agent to open the guided creation flow.
  2. Define the instructions and defaults. Add a name, description, prompt, optional skills, harness, model, environment, and secrets.
  3. Click Create agent. The saved agent appears on the Agents page and is available for runs.

For deeper guidance on reusable skills and team-scoped identities, see Skills as Agents and Agent identities.

Creating a new agent in the Oz web app.

Creating a new agent in the Oz web app.

The Skills page (/skills) is where you browse and run skills. Skills are reusable instruction sets stored in repositories, and agents can include one or more skills as part of their default configuration.

Use the From your Environments filter to view skills from repositories connected to your environments, or switch to Suggested to view recommended skills. Open a skill to view its activity, schedules, and SKILL.md configuration.

Click any skill to view its details, then click New run to start a run with that skill attached. You can also click New run from the page header to start a run with optional skill selection.

To create a skill for agents:

  1. Click New agent on the Skills page to open the skill creation flow.
  2. Choose a repository from an existing environment with GitHub access.
  3. Define the skill. Add a skill name, description, and instructions.
  4. Click Open Skill PR to create a pull request that adds the skill to the selected repository.

Creating a skill for agents in the Oz web app.

Creating a skill in the Oz web app.

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

The Schedules page (/schedules) lets you create and manage scheduled agents that run automatically on a cron schedule.

Each schedule displays:

FieldDescription
NameA descriptive name for the scheduled task
FrequencyHuman-readable description of the cron schedule (e.g., “Every Monday at 10am”)
Next runWhen the schedule will next execute
EnvironmentWhich environment the scheduled agent runs in
AgentWhich saved agent the schedule uses (if any)
StatusWhether the schedule is active or paused

The Schedules page in the Oz web app.

The Schedules page in the Oz web app.

To create a scheduled agent:

  1. Click New schedule in the header.
  2. Name the schedule. Use a descriptive name that explains what the scheduled agent does.
  3. Set the frequency. Choose a preset or enter a cron schedule.
  4. Select the environment where the scheduled agent should run.
  5. Choose a saved agent, if needed.
  6. Add the prompt that the agent should follow each time it runs.
  7. Click Create schedule. The schedule appears on the Schedules page.

Click any schedule to view its details and recent run history. From the detail pane, you can:

  • Edit the schedule configuration
  • Pause or enable the schedule
  • Delete the schedule
  • View past runs triggered by this schedule

The Environments page (/environments) shows all environments configured for your account. Environments define the execution context for cloud agents, including repos, Docker images, and setup commands.

Each environment displays:

FieldDescription
NameThe environment’s identifier
Docker imageThe container image used for execution
RepositoriesWhich repos the agent can access
Setup commandsCommands run before the agent starts

The Environments page in the Oz web app.

The Environments page in the Oz web app.

To create a new environment:

  1. Click New environment in the header.
  2. Name the environment. Use a descriptive name that explains the runtime context.
  3. Select the repositories the agent should be able to access.
  4. Choose a Docker image. Warp provides prebuilt dev images, or you can use your own.
  5. Add any setup commands that should run when the environment starts, such as npm install.
  6. Click Create environment. The environment appears on the Environments page.

The Integrations page (/integrations) lets you configure first-party integrations with Slack and Linear.

IntegrationDescription
SlackTag @Oz in messages or threads to trigger agents directly from Slack conversations
LinearTag @Oz on issues to trigger agents from your issue tracker

The Integrations page in the Oz web app.

The Integrations page in the Oz web app.

Click an integration to start the guided setup flow. You’ll authorize Warp to connect with the external service, select an environment, and configure any integration-specific settings.