Delegate bounded coding tasks to Oh My Pi and review diffs

Lets an orchestrating agent hand a bounded coding task to Oh My Pi (omp, the package @oh-my-pi/pi-coding-agent) as a separate implementer, then review what it produced and land it itself. Oh My Pi is a fork of the original Pi CLI, and the two are genuinely different binaries with different skills: this skill drives omp specifically, and if omp is missing but pi is installed, that install has Pi, not Oh My Pi, and needs the separate pi-delegate skill instead. Oh My Pi has no sandbox at all, and print mode has no approval UI, so a write-capable relay run always passes --yolo (tools.approvalMode: yolo) - without it, a user's always-ask or write config would simply stall the run until the watchdog fires. --read-only restricts omp's callable tools to read, grep, and glob instead (it does not pass --yolo), but installed extension code still runs with the user's host permissions if project resources are already trusted. The relay defaults to --no-extensions --no-skills --no-rules, keeping any project .omp extensions, skills, and rules undiscovered unless --approve is passed as an explicit opt-in for a repository the user actually trusts.

Model selection requires listing what the current install can actually run rather than guessing an id: omp --list-models no longer exists and is now treated as an unknown flag (exit 2), so discovery goes through the models subcommand (omp models, omp models --json, omp models find <substring>, or omp models <provider>), and --model <pattern> on the relay is then a fuzzy match against that live catalog - a bare id, a provider/id pair, or a unique substring - with --provider pinning the provider when the pattern is ambiguous. --thinking <level> is a separate reasoning dial (off/auto/minimal/low/medium/high/xhigh/max), and the relay rejects any other value (including inherit) before dispatch rather than letting omp silently warn and ignore it. A fleet lane's effort setting maps onto --thinking; an explicit --thinking/--model/--provider flag always wins over the lane. The relay pipes the brief to omp --mode json on stdin and writes a structured result.json; omp itself auto-loads AGENTS.md/CLAUDE.md context files from the workspace and its parents, so repo instructions reach it without being inlined into the brief.

Use it to delegate a bounded coding task to a separate omp implementer and then review its diff yourself, when the user explicitly asked for delegation to Oh My Pi. Do NOT use it when: the task is small enough to do inline and delegation overhead isn't worth it; the omp CLI is not installed or authenticated; the user actually asked for the original Pi CLI (pi) - use pi-delegate for that; or the task needs a genuinely sandboxed implementer, since Oh My Pi has none - --read-only narrows the tool surface, but a write-capable run executes unprompted under --yolo.

The brief states the goal, current state, what to change, what to leave untouched, the project's real gate commands, and a report contract telling omp not to commit. Dispatch:

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

Output is result.json with status (including omp_unavailable when the binary is missing), finalMessage (omp's own report), and touchedFiles (the review starting point). Rework resumes the most recent session (--resume-last) or a specific one (--session <id>) with just a delta brief.

Wraps the Oh My Pi CLI (installed via bun install -g @oh-my-pi/pi-coding-agent or the installer at omp.sh), authenticated with /login inside omp for a subscription provider or a provider API-key environment variable, with credentials stored under ~/.omp/. Provider/model catalog is whatever this specific install has authenticated, not a fixed list. Can apply a fleet lane's provider/model/effort dials from a companion delegate-setup configuration, though the relay does not forward omp's own --api-key, --smol, --slow, or --plan flags.

Orchestrating agents that need to delegate a scoped coding task to Oh My Pi specifically (not the original Pi CLI) and accept its no-sandbox, always---yolo headless model, verifying results through touchedFiles and the diff rather than a sandbox boundary. 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.