warp-delegate
Delegate a coding task to the Warp Agent CLI (`oz`) as a background implementer, then review its diff and land it yourself.
Install / Use
npx skills add amElnagdy/delegate-skills --skill warp-delegateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of warp-delegate
warp-delegate scores 89/100 on our quality scale, 1610th of 4,698 Development & Engineering skills we index (top 35%).
Its SKILL.md is 10 KB long, well organised into 23 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,181 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so warp-delegate is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
warp-delegate compared with similar skills
All 4 of these similar skills score higher than warp-delegate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| warp-delegate (this skill)by amElnagdy | 89 | 2.2k | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install warp-delegate?
- Run
npx skills add amElnagdy/delegate-skills --skill warp-delegate. The install tabs above show the steps for each supported agent. - Which AI agents does warp-delegate work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is warp-delegate safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is warp-delegate still maintained?
- The repository was last updated about 2 months ago, so warp-delegate is actively maintained.
Skill content
View source on GitHubname: warp-delegate
description: >-
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).
license: MIT
compatibility: Requires the oz CLI (Warp Agent CLI) installed and authenticated (oz login, or WARP_API_KEY for a headless host; Warp AI features need an eligible Warp plan or your own provider key), Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Shell examples assume bash/zsh (macOS/Linux, or Git Bash/WSL on Windows).
metadata:
version: 0.5.0
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 runexecutes 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 withDevice not configuredwhen 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
ozCLI is not installed or authenticated. - You need a sandboxed or read-only implementer.
oz agent runhas no sandbox, no permission mode, and no read-only run - see Autonomy and permissions. - The work must stay off Warp's servers.
oz agent runuploads an end-of-run workspace snapshot unless--no-snapshotis passed, and conversations live server-side.
Prerequisites (check once)
- Install the Warp Agent CLI - see https://docs.warp.dev/cli/.
- Authenticate:
oz login, or setWARP_API_KEYfor CI, a container, or any headless host. - Confirm the account has AI quota. A working login is not enough - unlike the other CLIs in
this package.
oz whoamican succeed while every dispatch fails withIn order to use Warp's AI features, subscribe to a Warp plan, or bring your own inference.Warp records this internally asQuotaLimit/ "lack of AI quota", so it is a credit condition on the account rather than a CLI-specific entitlement:ozruns the same agent harness as the Warp app and draws on the same account, plan, and credits. Check thatoz whoaminames the account holding the plan - if it does not,oz logout && oz loginfixes it. Otherwise confirm the plan's AI credits are not spent, or store your own provider key -warp --set-provider-api-key <openai|anthropic|google|grok>, or/api-keysinside the TUI. Bring-your-own-key needs no paid Warp plan. - Confirm
oz --versionsucceeds andoz whoamiprints your user. - Work in, or point
--cdat, the target git repository.
On macOS the CLI is distributed as a signed Developer ID binary; a first run may be held by Gatekeeper until it is approved.
Choose the model (optional)
Omit --model to use Warp's configured default. To pick another, choose an id from oz model list
and pass it verbatim. The relay accepts letters, digits, and . _ : / - only, so a value cannot be
mistaken for another oz flag.
The loop
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
1. Write the brief
Warp sees only the text you send plus what it can inspect in the workspace - no chat history or
shared context. Include the goal, current state, what to change, what to leave untouched, the
project's actual gates, and a report contract. Tell it not to commit. Keep one task per brief.
The brief is delivered as the --prompt value on argv, so it is visible in the host process list -
keep secrets out of it and reference workspace files instead. See
references/writing-the-brief.md.
2. Dispatch
Use the bundled relay. It runs oz agent run --output-format ndjson, captures the event stream, and
writes result.json. (<skill-dir> is the installed folder containing this SKILL.md.)
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# choose a model: add --model <id from oz model list>
# use an agent profile: add --profile <id>
# label the run: add --name <label>
# continue an existing conversation: add --conversation <id> (delta brief only)
# base the run on a Warp skill: add --skill <name|repo:name|org/repo:name>
# start MCP servers: add --mcp <path-or-inline-json> (repeatable)
# suppress the workspace snapshot upload: add --no-snapshot
# hard time limit (watchdog): add --timeout 2h (the 30m default suits short runs; implementation briefs routinely need 1-2h)
# see all options: node .../relay.mjs --help
The relay pins the workspace with both the child process's cwd and Warp's own --cwd. It writes
artifacts under the system temp dir by default and never commits. See
references/dispatch-and-poll.md.
3. Wait for completion
The relay blocks until oz finishes. Run it with the orchestrator's background-command facility, or
background it in the shell and poll for result.json. A pre-run usage error exits 2 and writes no
result; a missing oz exits 127 and writes status: "warp_unavailable".
Trust process state and the working tree over a progress display. Completion means the process
exited and result.json exists. Warp's report is the finalMessage field in result.json (also
printed on stdout between the report markers); the raw event stream is always in events.jsonl.
4. Review - do not trust the self-report
Treat Warp's final message and gate claims as claims:
- Re-run the project's gates yourself.
- Read the diff against the brief, starting with
touchedFiles. - Run relevant guard skills if installed.
- Round-trip migrations and grep for dangling references after removals or renames.
Because there is no read-only mode to fall back on, the diff is the only record you get - and it records what git can see in the workspace afterward, not everything the run did. Dispatch from a clean tree so the two are as close as they can be. See references/review-and-land.md.
5. Land it
The implementer edits the working tree; the orchestrator commits. Commit only after the gates
pass and the diff holds. If rework is needed, send a delta brief with --conversation <id> using the
conversationId from result.json, then review again.
Autonomy and permissions
oz agent run has no sandbox, no permission mode, and no read-only mode. A headless run reads,
writes, edits, and executes commands with your own user permissions and never prompts. There is
nothing in the CLI to restrict that surface, so this relay ships no --read-only flag - offering one
would imply an enforcement that does not exist. The controls you actually have are:
- Scope by directory.
--cdpins the workspace, and the relay passes it to Warp's own--cwd. Treat this as aim, not a fence: on oz 0.2026.05.27 shell commands did run in the pinned workspace, but the agent's file tool resolved bare relative paths against$HOME. Name absolute paths in the brief - see references/writing-the-brief.md. - Review the diff.
touchedFilesisgit status --porcelaintaken after the run - post-run, git-visible worktree state, not a log of what the agent did. It cannot show an ignored file, an edit the run made and then reverted, or a write outside the repository (see item 1), and it carries anything that was already dirty before dispatch. Dispatch from a clean tree so those are the same set, and treat the diff as the best available record, not a complete one. - Snapshot egress.
--no-snapshotforwards Warp's flag so the end-of-run workspace snapshot is not uploaded. Without it, the upload is Warp's default.
--auto-approve belongs to the interactive warp TUI and has no bearing on oz agent run.
Authorization model
Delegation is something the human opts into. Once they have ("run this queue", "proceed"), committing verified, gate-passing work is the agreed contract. Two limits remain: surface, don't absorb (report Warp's design decisions, defensible-but-unasked turns, and non-blocking nitpicks) and stop for scope changes (if correct completion needs going beyond the brief, ask instead of expanding the mandate). See references/review-and-land.md.
References
- references/writing-the-brief.md - structure, report contract, real gates, argv delivery, and delta briefs.
- references/dispatch-and-poll.md - flags, artifacts,
result.json, polling, and failure recovery. - references/review-and-land.md - review checklist, commit boundary, and rework through Warp conversations.
- references/multi-task-queues.md - sequential queues, constraint carry-forward, progress tracking, and the final coherence pass.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
