diff --git a/src/content/docs/agents/capabilities/computer-use/index.mdx b/src/content/docs/agents/capabilities/computer-use/index.mdx index 3cbd73ae2..02a7fb26e 100644 --- a/src/content/docs/agents/capabilities/computer-use/index.mdx +++ b/src/content/docs/agents/capabilities/computer-use/index.mdx @@ -135,3 +135,4 @@ Computer Use can also help with general web tasks: browsing websites, filling ou * [Images as Context](/agents/local-agents/agent-context/images-as-context/) - Pass design mockups and screenshots as context * [Full Terminal Use](/agents/capabilities/full-terminal-use/) - Let agents drive interactive terminal apps, see live output, and run commands +* [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) - Open the cloud run transcript and artifacts after a Computer Use session finishes diff --git a/src/content/docs/agents/capabilities/slash-commands.mdx b/src/content/docs/agents/capabilities/slash-commands.mdx index 41639fb63..69dd87c98 100644 --- a/src/content/docs/agents/capabilities/slash-commands.mdx +++ b/src/content/docs/agents/capabilities/slash-commands.mdx @@ -18,7 +18,7 @@ As you type, the menu filters results in real time, making it easy to find and r Warp currently supports the following built-in Slash Commands: -
Slash CommandDescription
/add-mcpAdd a new MCP server.
/add-promptAdd a new Agent Prompt in Warp Drive.
/add-ruleAdd a new Global Rule for the Agent.
/agentStart a new agent conversation. Optionally include a prompt to send immediately.
/changelogOpen the latest Warp changelog.
/cloud-agentStart a new cloud agent conversation. {'*'}
/compactFree up context by summarizing conversation history.
/compact-andCompact the current conversation and then send a follow-up prompt.
/continue-locallyFork the current cloud agent conversation into a local Warp session. See Handoff between local and cloud agents. Available while a cloud agent conversation is active.
/conversationsOpen conversation history.
/copy-debugging-idCopy debugging information for the current conversation to your clipboard, so you can include it when reporting an issue. Available while a conversation is active.
/costToggle credit usage details in the current conversation.
/create-environmentCreate a Warp Environment (Docker image + repos) via guided setup. {'*'}
/create-new-projectHave the Agent walk you through creating a new coding project. {'*'}
/environmentSwitch the environment for the current cloud agent conversation.
/export-to-clipboardExport the current conversation to clipboard in markdown format.
/export-to-fileExport the current conversation to a markdown file.
/feedbackOpen the static feedback experience. See Using /feedback in Warp for details.
/forkForks the current conversation into a new thread with the full context and history of the original.

You can optionally include a prompt that will be sent immediately in the forked conversation.
/fork-and-compactForks the current conversation and automatically compacts the forked version.

Useful when you want a fresh, summarized starting point that preserves relevant context while trimming the rest.
/fork-fromOpen a searchable menu to fork the conversation from a specific query. Select a query to create a fork that includes everything up to that point.
/handoffHand the current local conversation off to a cloud agent, carrying its history and a snapshot of your uncommitted changes. See Handoff from local to cloud. You can optionally include a follow-up prompt. {'*'}
/harnessSwitch the harness for the current cloud agent conversation.
/hostSwitch the execution host for the current cloud agent conversation.
/indexIndex the current codebase using Codebase Context.
/initIndex the current codebase and generate an AGENTS.md file. {'*'}
/modelSwitch the base agent model for the current conversation.
/newStart a new agent conversation (alias for /agent).
/open-code-reviewOpen the code review pane.
/open-fileOpen a file for editing in Warp's code editor.
/open-mcp-serversView the status of your MCP servers.
/open-project-rulesOpen the Project Rules file (AGENTS).
/open-repoSwitch to another indexed repository.
/open-rulesView all of your global and project rules.
/open-settings-fileOpen the Warp settings file (settings.toml) in Warp's code editor.
/open-skillOpen an interactive menu to browse and edit project or global skills.
/orchestrateBreak a task into subtasks and run them in parallel with multiple agents. See Multi-agent orchestration. {'*'}
/planPrompt the Agent to do some research and create a plan for a task.
/profileSwitch the active execution profile.
/promptsSearch saved prompts.
/queueQueue a prompt to send after the agent finishes responding. See Prompt Queueing.
/remote-controlPublish the current third-party CLI agent session to the cloud so you can monitor and steer it from another device. See Remote Control.
/rename-conversationRename the current conversation.
/rename-tabRename the current tab. Include the new tab name as an argument (for example, /rename-tab deploy).
/rewindRewind to a previous point in the conversation.
/set-tab-colorSet the color of the current tab. Takes a required color argument: red, green, yellow, blue, magenta, cyan, or none to clear it. See Tab colors.
/skillsInvoke a skill from a searchable menu.
/usageOpen billing and usage settings.
+
Slash CommandDescription
/add-mcpAdd a new MCP server.
/add-promptAdd a new Agent Prompt in Warp Drive.
/add-ruleAdd a new Global Rule for the Agent.
/agentStart a new agent conversation. Optionally include a prompt to send immediately.
/changelogOpen the latest Warp changelog.
/cloud-agentStart a new cloud agent conversation. {'*'}
/compactFree up context by summarizing conversation history.
/compact-andCompact the current conversation and then send a follow-up prompt.
/continue-locallyFork the current cloud agent conversation into a local Warp session. See Handoff between local and cloud agents. Available while a cloud agent conversation is active.
/conversationsOpen conversation history.
/copy-debugging-idCopy debugging information for the current conversation to your clipboard, so you can include it when reporting an issue. Available while a conversation is active.
/costToggle credit usage details in the current conversation.
/create-environmentCreate a Warp Environment (Docker image + repos) via guided setup. {'*'}
/create-new-projectHave the Agent walk you through creating a new coding project. {'*'}
/environmentSwitch the environment for the current cloud agent conversation.
/export-to-clipboardExport the current conversation to clipboard in markdown format.
/export-to-fileExport the current conversation to a markdown file.
/feedbackOpen the static feedback experience. See Using /feedback in Warp for details.
/forkForks the current conversation into a new thread with the full context and history of the original.

You can optionally include a prompt that will be sent immediately in the forked conversation.
/fork-and-compactForks the current conversation and automatically compacts the forked version.

Useful when you want a fresh, summarized starting point that preserves relevant context while trimming the rest.
/fork-fromOpen a searchable menu to fork the conversation from a specific query. Select a query to create a fork that includes everything up to that point.
/handoffHand the current local conversation off to a cloud agent, carrying its history and a snapshot of your uncommitted changes. See Handoff from local to cloud. You can optionally include a follow-up prompt. {'*'}
/harnessSwitch the harness for the current cloud agent conversation.
/hostSwitch the execution host for the current cloud agent conversation.
/indexIndex the current codebase using Codebase Context.
/initIndex the current codebase and generate an AGENTS.md file. {'*'}
/modelSwitch the base agent model for the current conversation.
/newStart a new agent conversation (alias for /agent).
/open-code-reviewOpen the code review pane.
/open-fileOpen a file for editing in Warp's code editor.
/open-mcp-serversView the status of your MCP servers.
/open-project-rulesOpen the Project Rules file (AGENTS).
/open-repoSwitch to another indexed repository.
/open-rulesView all of your global and project rules.
/open-settings-fileOpen the Warp settings file (settings.toml) in Warp's code editor.
/open-skillOpen an interactive menu to browse and edit project or global skills.
/orchestrateBreak a task into subtasks and run them in parallel with multiple agents. See Multi-agent orchestration. {'*'}
/planPrompt the Agent to research and create a plan for a task. When the work benefits from parallel agents, the plan can include multi-agent orchestration.
/profileSwitch the active execution profile.
/promptsSearch saved prompts.
/queueQueue a prompt to send after the agent finishes responding. See Prompt Queueing.
/remote-controlPublish the current third-party CLI agent session to the cloud so you can monitor and steer it from another device. See Remote Control.
/rename-conversationRename the current conversation.
/rename-tabRename the current tab. Include the new tab name as an argument (for example, /rename-tab deploy).
/rewindRewind to a previous point in the conversation.
/set-tab-colorSet the color of the current tab. Takes a required color argument: red, green, yellow, blue, magenta, cyan, or none to clear it. See Tab colors.
/skillsInvoke a skill from a searchable menu.
/usageOpen billing and usage settings.
:::caution Slash commands marked with a `*` consume credits to complete the task. diff --git a/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx b/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx index a7a3ff042..ac87b90c4 100644 --- a/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx @@ -232,7 +232,7 @@ Cloud orchestration is the best fit when you need: Do not merge every agent's output automatically. Use a fan-in pass: 1. Review each agent's summary, changed files, and validation results. -2. Open the [Code Review panel](/code/code-review/) for local branches, or inspect cloud run artifacts and session links for cloud children. +2. Open the [Code Review panel](/code/code-review/) for local branches, or use [session sharing](/platform/viewing-cloud-agent-runs/) to inspect cloud children's artifacts and session links. 3. Merge or cherry-pick one branch at a time. 4. Re-run the full validation suite from the final integrated branch. 5. Attach context for reviewers: agent session links, changed files, validation commands, known risks, and reviewer asks. @@ -241,7 +241,7 @@ For GitHub handoff, see [Attach agent session context to GitHub PRs](/guides/age ## Productivity tips -* **Use the Agent Management Panel** — Open the Agent Management Panel to see all active agents across tabs. This gives you a dashboard view of what's running, what's waiting, and what's finished. +* **Use the [Agent Management Panel](/platform/managing-cloud-agents/)** — Open it to see all active agents across tabs. This gives you a dashboard view of what's running, what's waiting, and what's finished. * **Color-code your tabs** — Assign different themes or colors to agent tabs so you can visually distinguish them at a glance in the vertical sidebar. * **Compose with `Ctrl+G`** — Use Warp's rich input editor (`Ctrl+G`) when composing prompts for third-party agents. This gives you click-to-edit instead of arrow-key navigation in the raw CLI. * **Review all changes before committing** — After running multiple agents, open the Code Review panel to see the combined diff across all files. Use "Changes vs. main" view to see the full scope of all agent-generated changes on your branch. diff --git a/src/content/docs/guides/agent-workflows/run-a-software-factory-in-the-cloud.mdx b/src/content/docs/guides/agent-workflows/run-a-software-factory-in-the-cloud.mdx index 6167264f4..d104bf216 100644 --- a/src/content/docs/guides/agent-workflows/run-a-software-factory-in-the-cloud.mdx +++ b/src/content/docs/guides/agent-workflows/run-a-software-factory-in-the-cloud.mdx @@ -28,7 +28,7 @@ The practical difference: * **Per-agent permissions** — Your triage agent only needs to read issues and post comments. Your implementation agent needs to push branches and open PRs. Each agent gets exactly the permissions it needs, not a single shared credential that everything uses. * **Audit trails** — Every cloud agent run is logged separately. You can see exactly what the triage agent did versus what the implementation agent did, when it ran, and what it produced. -* **Team visibility** — Any teammate can open a run in the {VARS.WEB_APP} to inspect the session transcript, steer a stuck agent, or pick up where the agent left off. +* **Team visibility** — Any teammate can open a run in the {VARS.WEB_APP} to inspect the session transcript, steer a stuck agent, or [hand the work off](/platform/handoff/) to keep going from another session. * **Scale without contention** — Multiple triage runs can execute in parallel without fighting over a shared dev box, local git checkouts, or CPU. See [Deployment patterns](/platform/deployment-patterns) for a full comparison of {VARS.WARP_AUTOMATION_PLATFORM}-hosted, CLI-based, and self-hosted execution patterns. @@ -78,9 +78,9 @@ Every cloud agent run in your factory appears in the {VARS.DASHBOARD} with: * Status history: queued, in progress, succeeded, or failed with error details * A session sharing link any teammate can open to inspect or steer the run -Open runs from {VARS.WEB_APP_URL} or from the **Agent Management Panel** in the Warp app. Include the session link in PR descriptions so reviewers can see exactly how the agent built the change — see [Attach agent context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs). +Open runs from the [{VARS.WEB_APP}](/platform/oz-web-app/) or from the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app. Include the session link in PR descriptions so reviewers can see exactly how the agent built the change — see [Attach agent context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/). -See [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs) for the full reference. +See [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) for the full reference. ## 5. Use multi-agent orchestration for large backlogs diff --git a/src/content/docs/platform/oz-web-app.mdx b/src/content/docs/platform/oz-web-app.mdx index b40860d23..f67456ce1 100644 --- a/src/content/docs/platform/oz-web-app.mdx +++ b/src/content/docs/platform/oz-web-app.mdx @@ -62,7 +62,7 @@ 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. +Click any run to open the detail pane, where you can view the full transcript, artifacts, and metadata. For the full walkthrough of opening, steering, and forking a session, see [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/). ### Filtering and search @@ -246,6 +246,7 @@ For detailed integration setup instructions, see [Slack](/platform/integrations/ ## Related resources * [Cloud Agents overview](/platform/) — Learn about cloud agents and when to use them +* [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) — Open, inspect, and continue a cloud agent session from Warp or the browser * [Multi-agent orchestration](/platform/orchestration/) — Parent/child model and common orchestration patterns * [Skills as Agents](/platform/skills-as-agents/) — Run agents based on reusable skill definitions * [Scheduled Agents](/platform/triggers/scheduled-agents/) — Run agents automatically on a cron schedule diff --git a/src/content/docs/platform/viewing-cloud-agent-runs.mdx b/src/content/docs/platform/viewing-cloud-agent-runs.mdx index 12cb6f3b1..090e143f0 100644 --- a/src/content/docs/platform/viewing-cloud-agent-runs.mdx +++ b/src/content/docs/platform/viewing-cloud-agent-runs.mdx @@ -24,7 +24,7 @@ This makes cloud agent runs observable, steerable, and collaborative — even if With cloud agent session sharing, you can view the full remote session for a cloud agent run and: * See every command the agent executed in the virtual environment -* Inspect context, logs, and outputs directly in Warp or the web viewer +* Inspect context, logs, outputs, and [Computer Use](/agents/capabilities/computer-use/) artifacts * Review the prompt, plan, task list, and decisions that led to the result * Ask follow-up questions or give additional instructions after the task completes * Bring the conversation into your local Warp session with Fork to local @@ -105,6 +105,7 @@ You get consistent visibility into the work regardless of where you open it. * [Managing cloud agents](/platform/managing-cloud-agents/) — Find cloud agent runs by source, status, trigger, or owner. * [Multi-agent orchestration](/platform/orchestration/) — Inspect parent and child cloud runs that fan work out in parallel. +* [Computer Use](/agents/capabilities/computer-use/) — Review GUI and browser work performed by a cloud agent inside its sandbox. * [Remote Control](/agents/cli-agents/remote-control/) — Publish a third-party CLI agent session to monitor and steer it from another device. * [Attach agent session context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/) — Share a run link with a PR so reviewers can inspect the agent's execution context. * [Agent Session Sharing](/agents/local-agents/session-sharing/) — Share local Warp agent or third-party CLI agent sessions.