Agent skill · amelnagdy
warp-delegate
Delegate a coding task to the Warp Agent CLI (`oz`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Warp - phrasings like "have Warp implement X", "delegate this to the Warp CLI", "run it through Warp", "use oz to implement/fix/refactor" - or wants to run a queue of coding tasks through Warp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or for the interactive `warp` TUI (this skill drives the headless `oz agent run`, not the terminal app).
What it needs
About 6k tokens when loaded.
What this skill does
Warp Delegate You are the orchestrator. Delegate a bounded coding task to a separate implementer - the Warp Agent CLI - then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own conversation; you verify and commit. The loop needs only a shell command and file access, so any comparable orchestrator can drive it. The binary is oz, not warp Warp ships two different programs, and only one of them can be delegated to: oz - the Warp Agent CLI. Headless and scriptable; oz agent run executes an agent against a local directory. This is what the relay drives. warp - the interactive Warp TUI. It requires a terminal device, has no prompt or print flag (its only options are --resume, --auto-approve, --api-key, and the provider-key commands), and exits with Device not configured when stdin is a pipe. It cannot be relayed. If oz is missing but warp is installed, you have the TUI, not the CLI. When NOT to use this The task is small enough to do inline; delegation overhead is not worth it. The oz CLI is not installed or authenticated. You need a sandboxed or read-only implementer. oz agent run has no sandbox, no permission mode, and no read-only run - see Autonomy and permissions. The work must stay off Warp's servers. oz agent run uploads an end-of-run workspace snapshot unless --no-snapshot is passed, and conversations live server-side. Prerequisites (check once) 1. Install the Warp Agent CLI - see <https://docs.warp.dev/cli/>. 2. Authenticate: oz login, or set WARPAPIKEY for CI, a container, or any headless host. 3. Confirm the account has AI quota. A working login is not enough - unlike the other CLIs in this package. oz whoami can succeed while every dispatch fails with In order to use Warp's AI features, subscribe to a Warp plan, or bring your own inference. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills amelnagdy/warp-delegate