Fast follow 2: refine orchestrate launch docs#117
Conversation
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 |
There was a problem hiding this comment.
Overview
This PR refines the cloud agent harness documentation for Warp Agent, Claude Code, Codex, and the harness overview, including clearer credential setup language and two new screenshots. I did not find correctness, security, style, or structure issues that need changes before merge.
Concerns
- No blocking concerns found.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
|
Pushed a scoped follow-up for the Oz web app launch docs review in What changed and why:
Validation:
|
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
left a comment
There was a problem hiding this comment.
nice, ty for the screenshots!
| --- | ||
|
|
||
| Oz can run third-party agents — [Claude Code](/agent-platform/cloud-agents/harnesses/claude-code/) and [Codex](/agent-platform/cloud-agents/harnesses/codex/) — as cloud agents alongside Warp Agent. You choose the harness (agent runtime) that fits the task; the platform around the run stays the same. | ||
| Oz can run two third-party agents as cloud agents alongside Warp Agent: [Claude Code](/agent-platform/cloud-agents/harnesses/claude-code/) and [Codex](/agent-platform/cloud-agents/harnesses/codex/). You choose the harness (agent runtime) that fits the task; the platform around the run stays the same. |
There was a problem hiding this comment.
i wouldn't specify just two, since we'll be adding support for many others soon!
|
|
||
| 1. A Warp Agent parent run analyzes a task and breaks it into subtasks. | ||
| 2. The parent dispatches Claude Code subagents for code-review-heavy steps and Codex subagents for high-volume edits. | ||
| 2. The parent dispatches Claude Code subagents for steps that require code review or nuanced judgment and Codex subagents for high-volume edits. |
There was a problem hiding this comment.
can we use simpler language here than "nuanced judgement"?
| * **Skills** - Skill specs (for example, `org/repo:path/to/SKILL.md`) the identity comes preloaded with. Shorthand specs like `repo:skill_name` are accepted when they resolve unambiguously against the team's cloud environments. | ||
|
|
||
| Skill specs are stored in their normalized fully-qualified form, and managed secret references are validated against the team's secret scope at attach time. If a secret is missing or a skill repo is not accessible to the team's GitHub App installation, the request is rejected before anything is saved. | ||
| Warp saves each skill spec with its full repository reference, so shorthand specs like `repo:skill_name` are resolved before they are stored. Managed secret references are validated against the team's secret scope at attach time. If a secret is missing or a skill repo is not accessible to the team's GitHub App installation, the request is rejected before anything is saved. |
There was a problem hiding this comment.
I think we can keep this generally high level, I don't think we need to expose this internal implementation detail perhaps?
Summary
This PR is a broad fast-follow to the Cloud Agents launch docs. Changes are grouped by file below.
Terminology note
Following team clarification, this PR treats agent identity as an implementation/API detail, not a product-facing concept. The Oz web app article now uses agents for the product surface and removes references to “agent identity/identities” except when linking to the existing Agent identities page. That reference page is left in place for now and will be simplified to agents in follow-up work.
src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx/dashboardentry, adds/skills, and clarifies the split between Agents and Skills.src/content/docs/agent-platform/cloud-agents/agents.mdxsrc/content/docs/agent-platform/cloud-agents/harnesses/index.mdxsrc/content/docs/agent-platform/cloud-agents/harnesses/warp-agent.mdxsrc/content/docs/agent-platform/cloud-agents/harnesses/claude-code.mdxsrc/content/docs/agent-platform/cloud-agents/harnesses/codex.mdxsrc/content/docs/agent-platform/cloud-agents/harnesses/authentication.mdxsrc/assets/agent-platform/oz-web-app-runs-view.pngsrc/assets/agent-platform/oz-web-app-agents.pngsrc/assets/agent-platform/oz-web-app-new-agent.pngsrc/assets/agent-platform/oz-web-app-new-skill.pngsrc/assets/agent-platform/claude-code-auth-secret-setup.pngsrc/assets/agent-platform/cloud-agent-harness-selector-warp-app.pngValidation
git diff --checknpm run buildConversation: https://staging.warp.dev/conversation/db4886fb-3576-4fbc-b694-e8f0852e4bb0
Co-Authored-By: Oz <oz-agent@warp.dev>