Agents > Oz Cloud Agents & Orchestration

Managing cloud agents

Monitor and manage agent activity across your team with Warp's Agent Management Panel and the Oz web app's Runs page.

Warp provides two management surfaces for tracking and observing agent activity across your account and, where applicable, your team: the Agent Management Panel in the Warp app and the Runs page in the Oz web app, which also works on mobile devices.

Use these surfaces as the starting point for real-time agent observability in Warp. They help you see which agents are active, which runs are blocked or failed, where each run started, and which session link opens the prompt, plan, commands, logs, outputs, and follow-up messages behind the work.

The Agent Management Panel and Oz web app Runs page are designed to answer, at a glance:

Which agents are active or have been running recently.
Which runs are working, blocked, failed, succeeded, or canceled.
Where an agent run was triggered from, such as a local agent conversation, the Oz CLI, Slack, Linear, a schedule, or the API.
How parent and child runs relate in orchestrated workflows.
Which session to open when you need prompt, plan, command, log, output, or follow-up context.
How many credits those runs consumed.

Warp’s agent observability is run- and session-oriented. It is not a replacement for full APM, OpenTelemetry, or Datadog-style tracing across arbitrary agent frameworks. Use Warp to track agent run status, trigger/source, owner, parent-child relationships, transcripts, commands, logs, outputs, and replayable session links.

These management surfaces include your local (interactive) agents and cloud agent runs.

Warp's Agent Management Panel showing interactive and cloud agent runs. — Warp’s Agent Management Panel showing interactive and cloud agent runs.

What appears in the agent management surfaces

The Agent Management Panel and Oz web app Runs page include two categories of agent activity.

Interactive agents

Initiated from the Warp app.
The conversation is owned by you. It opens locally in Warp, and can be shared via a link when needed.
Credit usage reflects inference.

Cloud agent runs

Background executions initiated by triggers such as integrations and automations (for example: Slack, Linear, schedules, GitHub Actions, or API/CLI invocations).
Each run produces a shared session that can be inspected after completion (including logs, messages, and outputs).
Credit usage reflects inference + compute, shown as a single combined value in this view.

In the Personal tab, you can view all of the interactive and cloud agent conversations that you own. In the All tab, you can see everything from the personal tab, as well as any cloud agent sessions that are shared with you by your teammates; right now, this only includes things triggered from integrations.

Inspect or review an agent run

Use the Agent Management Panel or Oz web app Runs page as the starting point when a teammate asks, “What did the agent do?”

In the agents list, use the filter menu to filter by source, day, creator, or status.
Select the matching row to open the shared session or local conversation.
Inspect the prompt, plan, commands, logs, outputs, and follow-up messages where available.
Share the session link with teammates if they need to review the same context.
For PR-producing workflows, include the session link alongside the PR link so reviewers can inspect both the code diff and the agent’s execution context.

For cloud agent runs, the session opens in Cloud agent session sharing. For local interactive agents, the conversation opens in Warp and can be shared with Agent Session Sharing.

The agents list

Each row represents a single item in the agents list (either an interactive conversation or a cloud agent run). The list is intended to be scannable: you should be able to understand “what happened” without opening anything.

Fields you’ll see

Source

Where the agent was launched from. Common sources include:

Interactive: an agent conversation started in the Warp app
CLI: a local run triggered by the Oz CLI
API: a run triggered by Warp’s API
Slack / Linear: runs triggered by integrations
Scheduled: runs triggered on a cron schedule

Status

Warp uses a small set of statuses to help you quickly identify what needs attention:

Status	Icon	Description
`Working`	N/A	in progress (may include queued / running states)
`Blocked`	🟨	(interactive only) the conversation is waiting on user input or a required step
`Canceled`	⬜️	(interactive only) the interactive conversation was canceled before completion
`Failed / Errored`	🔺	something went wrong (applies to both interactive and cloud agent runs)
`Success`	✅	completed successfully (applies to both interactive and cloud agent runs)

Duration (for cloud agent tasks)

Shown for cloud agent runs to indicate how long the task executed.
Note: Interactive conversations generally don’t map cleanly to a single “run duration,” so this is currently omitted.

Inspecting an agent

The primary interaction is simple:

Clicking a cloud agent row opens the shared session for that run (prompt, plan, commands, logs, messages, and output where available).
Clicking an interactive row opens the conversation locally in the Warp app.

This makes the agents list a navigation surface: find the thing you care about, click once, and you’re in the right context to inspect or continue work.

Filtering

In both Personal and All views, you can open the filter menu and filter by:

Source (interactive, API, CLI, Slack/Linear, scheduled)
Day of creation
Creator
Status

This is the fastest way to isolate “everything that failed today,” “runs from Slack,” or “what a specific teammate triggered via integrations.”

Orchestrated runs (parent and child)

When a parent agent spawns one or more child agents through multi-agent orchestration, the parent and each child are tracked as separate runs. Where you see them depends on the surface:

Local children in the Warp app - while you’re viewing the parent agent, an orchestration pill bar above the agent view header shows one pill per child with a live status badge. Click a child pill to switch the pane to that child’s conversation in place; click the parent pill - or the breadcrumb that replaces the pill bar while you’re viewing a child - to return. Local children don’t appear as separate rows in the Agent Management Panel list.
Cloud children in the Warp app - appear in the Agent Management Panel list as their own rows alongside the parent and other runs. Filter by source, status, or creator to isolate them.
Cloud children in the Oz web app - grouped under the parent’s row on the Runs page, and surfaced together inside the parent’s detail pane on a Sub-agents tab.

The parent’s own status reflects only its work - a parent can finish successfully while a child is still running or has failed. To verify that an orchestration completed, check each child individually from the pill bar (in the Warp app) or the Sub-agents tab (in the Oz web app).

Cloud agents overview — What cloud agents are and when to use them.
Multi-agent orchestration — Parent/child model, run state transitions, and common orchestration patterns.
Viewing cloud agent runs — Open and inspect a remote cloud agent run.
Handoff between local and cloud agents — Move agent work between local and cloud, or continue a finished cloud run.
Oz web app — Manage runs and schedules from any browser.