warp-delegate

1# Warp Delegate
2 
3You are the **orchestrator**. Delegate a bounded coding task to a separate **implementer** - the
4Warp Agent CLI - then review what it produced and land it yourself. You write the brief and own the
5judgment; the implementer makes changes in its own conversation; you verify and commit.
6 
7The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
8 
9## The binary is `oz`, not `warp`
10 
11Warp ships two different programs, and only one of them can be delegated to:
12 
13- **`oz`** - the Warp Agent CLI. Headless and scriptable; `oz agent run` executes an agent against a
14  local directory. **This is what the relay drives.**
15- **`warp`** - the interactive Warp TUI. It requires a terminal device, has no prompt or print flag
16  (its only options are `--resume`, `--auto-approve`, `--api-key`, and the provider-key commands),
17  and exits with `Device not configured` when stdin is a pipe. It cannot be relayed.
18 
19If `oz` is missing but `warp` is installed, you have the TUI, not the CLI.
20 
21## When NOT to use this
22 
23- The task is small enough to do inline; delegation overhead is not worth it.
24- The `oz` CLI is not installed or authenticated.
25- You need a sandboxed or read-only implementer. `oz agent run` has **no sandbox, no permission
26  mode, and no read-only run** - see [Autonomy and permissions](#autonomy-and-permissions).
27- The work must stay off Warp's servers. `oz agent run` uploads an end-of-run workspace snapshot
28…