Managing cloud agents

Warp provides a centralized management view where you can monitor agent activity across your account and (where applicable) your team. You can access this view in the Warp app or through the Oz web app at oz.warp.dev, which works on mobile devices.

The management view is designed to answer, at a glance:

• Which agents have been running recently (and what’s running right now)
• Which runs succeeded, failed, or were canceled
• Where an agent run was triggered from (a local agent conversation, the Oz CLI, Slack, etc.)
• How many credits those runs consumed

This management view includes your local (interactive) agents and cloud agent runs.

Warp’s management view showing interactive and cloud agent runs.

What appears in the management view

The management view includes two categories of agent activity.

Interactive agents

• Initiated from the Warp desktop 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.

Caution

All usage rolls up into Warp’s standard credit system.

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.

---

The agents list

Each row represents a single item in the management view (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 (logs/messages/output).
• Clicking an interactive row opens the conversation locally in the Warp app.

This makes the management view 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 management view list.
• Cloud children in the Warp app - appear in the management view 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).

Related pages

• 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.