docs: document oz agent run-cloud harness flags#322
Conversation
Add --harness, --claude-auth-secret, and --codex-auth-secret to the oz agent run-cloud CLI reference, plus a "Choosing an execution harness" example. 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 documents the oz agent run-cloud harness selection and auth-secret flags in the CLI reference.
Concerns
- The key-flags list now repeats the
--claude-auth-secretand--codex-auth-secretentries that already exist immediately above the added lines. - The new "Choosing an execution harness" subsection duplicates the third-party harness setup paragraph and example that already appear right after the key-flags list.
Verdict
Found: 0 critical, 2 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
| * `--harness <HARNESS>` — choose the [execution harness](/platform/harnesses/) for the run: `oz` (default, Warp's built-in agent infrastructure), `claude` (Claude Code), or `codex`. | ||
| * `--claude-auth-secret <NAME>` — name of the [Warp-managed secret](/platform/harnesses/authentication/) that authenticates the Claude Code harness. Only valid with `--harness claude`. | ||
| * `--codex-auth-secret <NAME>` — name of the [Warp-managed secret](/platform/harnesses/authentication/) that authenticates the Codex harness. Only valid with `--harness codex`. |
There was a problem hiding this comment.
--claude-auth-secret and --codex-auth-secret twice. Replace this range with only the new --harness entry (or edit the existing entries in place).
| * `--harness <HARNESS>` — choose the [execution harness](/platform/harnesses/) for the run: `oz` (default, Warp's built-in agent infrastructure), `claude` (Claude Code), or `codex`. | |
| * `--claude-auth-secret <NAME>` — name of the [Warp-managed secret](/platform/harnesses/authentication/) that authenticates the Claude Code harness. Only valid with `--harness claude`. | |
| * `--codex-auth-secret <NAME>` — name of the [Warp-managed secret](/platform/harnesses/authentication/) that authenticates the Codex harness. Only valid with `--harness codex`. | |
| * `--harness <HARNESS>` — choose the [execution harness](/platform/harnesses/) for the run: `oz` (default, Warp's built-in agent infrastructure), `claude` (Claude Code), or `codex`. |
|
|
||
| You can reuse saved prompts with `--saved-prompt`, and reference notebooks, workflows, and rules inline in any `--prompt` string. See [Referencing Warp Drive objects](/reference/cli/warp-drive/) for details. | ||
|
|
||
| #### Choosing an execution harness |
There was a problem hiding this comment.
2 participants
Document the
--harness,--claude-auth-secret, and--codex-auth-secretflags foroz agent run-cloudin the CLI reference. These flags let you delegate a cloud run to a third-party coding agent (Claude Code or Codex) with the matching Warp-managed auth secret.What changed
oz agent run-cloudKey flags list inreference/cli/index.mdx.Source
Flags defined in
warp:crates/warp_cli/src/agent.rs(RunCloudArgs). All three are non-hidden (public) and theoz/claude/codexharness values are GA for cloud runs (Harness::should_display_in_help_text).Audit context
Found via the
missing_docsdrift-watch audit (surface_changes: new CLI flags on theagentcommand).Conversation: https://staging.warp.dev/conversation/693d79a7-7cf9-4a67-b070-2aeb15986da6
Run: https://oz.staging.warp.dev/runs/019f4cf8-d573-7793-af78-d05ffd29cfd5
This PR was generated with Oz.