Warp Delegate
Delegate a coding task to the Warp Agent CLI (`oz`) as a background implementer, then...
Install
npx skills add amElnagdy/delegate-skills --skill warp-delegate -g -a claude-code -y- Repository
- amElnagdy/delegate-skills2.5k
- Category
- AI and agents
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 2,499 tokens
- Runs scripts
- Yes, review before use
What it does
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).
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.
