Delegate bounded coding tasks to Warp CLI and review diffs

Lets an orchestrating agent hand a bounded coding task to the Warp Agent CLI as a separate implementer, then review what it produced and land it itself. Warp ships two different programs, and only one is delegable: oz, the headless, scriptable Warp Agent CLI (oz agent run executes an agent against a local directory) - this is what the relay drives - versus warp, the interactive Warp TUI, which requires a real terminal device, has no prompt or print flag, and exits with Device not configured the moment stdin is a pipe. If oz is missing but warp is installed, that machine has only the TUI, not the CLI this skill needs.

A login that succeeds is explicitly not enough to dispatch work: oz whoami can print a valid user while every dispatch still fails with "In order to use Warp's AI features, subscribe to a Warp plan, or bring your own inference" - Warp logs this internally as QuotaLimit, a credit condition on the account (since oz runs the same agent harness as the Warp desktop app and draws on the same plan and credits), not a CLI-specific entitlement. The fix is either confirming oz whoami names the account actually holding the plan, checking the plan's AI credits aren't spent, or storing a bring-your-own provider key (which needs no paid Warp plan at all) via warp --set-provider-api-key <openai|anthropic|google|grok> or the TUI's /api-keys.

oz agent run has no sandbox, no permission mode, and no read-only mode whatsoever - a headless run reads, writes, edits, and executes commands with the user's own permissions and never prompts, so the relay deliberately ships no --read-only flag at all, since offering one would imply an enforcement that doesn't exist. --cd pins the workspace via Warp's own --cwd, but this is aim, not a fence: on a past oz version, shell commands ran in the pinned workspace while the agent's file tool still resolved bare relative paths against $HOME instead - so the brief should name absolute paths rather than relative ones. Because there is no read-only fallback, touchedFiles (git status --porcelain taken after the run) is the only record available, and it only shows post-run git-visible worktree state - it cannot show an ignored file, an edit that was made and then reverted, or a write that landed outside the repository, which is exactly why dispatching from a clean tree matters. oz agent run also uploads an end-of-run workspace snapshot to Warp's servers by default (conversations themselves live server-side too), unless --no-snapshot is explicitly passed - a real consideration when the work must stay off Warp's infrastructure. The brief itself is delivered as the --prompt argv value, visible in the host process list, so secrets belong in workspace files, never inlined into the brief text.

Use it to delegate a bounded coding task to a separate Warp Agent CLI implementer and then review its diff yourself, when the user explicitly asked for delegation to it. Do NOT use it when: the task is small enough to do inline; the oz CLI is not installed or authenticated; the task needs a sandboxed or read-only implementer, since oz agent run offers neither; or the work must stay off Warp's servers, since a workspace snapshot uploads by default unless --no-snapshot is passed.

The brief states the goal, current state, what to change, what to leave untouched (with absolute paths where location matters), the project's real gate commands, and a report contract telling Warp not to commit. Dispatch:

node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo

Output is result.json with status (including warp_unavailable when the binary is missing), finalMessage, conversationId (for a delta-brief resume via --conversation <id>), and touchedFiles - plus the complete raw event stream in events.jsonl.

Wraps the Warp Agent CLI (oz, see docs.warp.dev/cli/), authenticated via oz login or a WARP_API_KEY for a headless host, drawing on the same account, plan, and AI credits as the Warp desktop app. Can name a specific model (oz model list), an agent profile, an existing Warp skill (--skill <name|repo:name|org/repo:name>), or start MCP servers inline. On macOS the CLI ships as a signed Developer ID binary that Gatekeeper may hold on first run.

Orchestrating agents that need to delegate a scoped coding task to the Warp Agent CLI and accept that no sandbox or read-only mode exists - verification rests entirely on a post-run diff from a clean tree, and any server-side snapshot upload needs to be weighed or suppressed. Adapted from the community amElnagdy/delegate-skills repository under the MIT license; this catalog entry is a docs-only import, since the executable scripts/relay.mjs is not bundled here.