docs(cli): cloud handoff and orchestration - #402
Conversation
Fill in cli/cloud-and-orchestration.mdx with the /handoff flow and what context carries over, resuming finished cloud runs from the conversation list, multi-agent orchestration (approval card, local and cloud children), and managing child agents via the agents tab bar. Cross-links the canonical platform/handoff and platform/orchestration pages. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR replaces the stub CLI cloud-and-orchestration page with full documentation for handoff, resuming cloud conversations, orchestration approval, and child-agent management. The content is broadly scoped to the intended page, and the provided artifacts do not surface security or spec-context concerns.
Concerns
- The new page hardcodes rename-sensitive Oz web app terminology and URL text instead of using the docs variable system. Apply the inline fix and update the other new
Oz web appreferences on this page the same way.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| Press `Ctrl+C` at any point before confirming to cancel the handoff; your prompt and attachments return to the input. | ||
|
|
||
| :::note | ||
| If you have no cloud environments yet, the card prompts you to create one: `Enter` opens the [Environments page in the Oz web app](https://oz.warp.dev/environments), and `R` refreshes the list after you create one. |
There was a problem hiding this comment.
Oz web app references on this page the same way.
| If you have no cloud environments yet, the card prompts you to create one: `Enter` opens the [Environments page in the Oz web app](https://oz.warp.dev/environments), and `R` refreshes the list after you create one. | |
| If you have no cloud environments yet, the card prompts you to create one: `Enter` opens the <a href={`${VARS.WEB_APP_URL}/environments`}>Environments page</a> in the {VARS.WEB_APP}, and `R` refreshes the list after you create one. |
{{WARP_CLI}} tokens aren't substituted in MDX frontmatter by the content
layer, so replace them with the literal product name in title/description.
Body prose keeps {VARS.WARP_CLI}.
Co-Authored-By: Oz <oz-agent@warp.dev>
…cli-cli-cloud-orchestration
Follows the confirmed launch name. Body prose picks up the new name via the WARP_CLI content variable from the base branch. Co-Authored-By: Oz <oz-agent@warp.dev>
1 participant
Pages changed
src/content/docs/cli/cloud-and-orchestration.mdx(replaces stub with full draft)Features covered
/handoffto a cloud agent: card flow (environment/model selection,Ctrl+Eediting, no-environment state), what context carries over (forked transcript, workspace snapshot incl. untracked files, pending prompt/images), created-card actions (Enteropen run,Ccontinue locally,Nnew conversation), and guardrails (active long-running command, in-progress/blocked children, orchestrator handoff keeps the tree local). Cross-links platform/handoff as canonical.←//conversations), continuing them locally, constraints (run must be finished; Warp Agent runs only), plus a--resumepointer to cli/conversations.Enter/Ctrl+E/Ctrl+C, config pages incl. location, model, and cloud harness/environment/host/API key), local children (own sessions, parent working directory, Warp Agent only), cloud children (live status view, run link to Oz web app, GitHub-auth blocker behavior, read-only caution). Cross-links platform/orchestration as canonical.Shift+↑tab bar focus and theShift + ↑ for other agentshint, keyboard navigation (Tab/arrows,Shift+←/Shift+→,↓,Esc), mouse clicks and overflow paging, retained per-session state, status-driven tab reordering, and interacting with a focused local child (follow-ups, approvals,Ctrl+Cto stop its response).Dropped/unconfirmed
Ctrl+Cfrom the tab bar: not shipped on master; the interrupt handler only stops the focused session's response or arms exit confirmation, so the page doesn't document it. Note for eng: the cloud orchestration tab-bar footer already advertises "Ctrl+C to kill sub-agent" even though no kill behavior exists yet.Suggested reviewer(s): harry
Validation:
npm run buildgreen (363 pages).Conversation: https://staging.warp.dev/conversation/d5677868-644c-4168-977e-87e0e973b0b3
Run: https://oz.staging.warp.dev/runs/019faa96-9e77-7cfa-bda7-699630df63ee
Co-Authored-By: Oz oz-agent@warp.dev