Delegate bounded coding tasks to Oh My Pi and review diffs

Drives Oh My Pi (omp, package @oh-my-pi/pi-coding-agent) as a separate coding implementer: you write a brief, dispatch it to omp in its own session, review what it produced, and land the commit yourself. Oh My Pi is a fork of Pi - the binary is omp, not pi. The original Pi CLI is a different binary with a different skill (pi-delegate); if omp is missing but pi is installed, that install has Pi, not Oh My Pi.

The loop has five steps. Steps 1, 4, and 5 need judgment; 2 and 3 are mechanical:

1. Write the brief. Oh My Pi sees only the text sent to it plus what it can inspect in the workspace - no chat history or shared context. The brief should include the goal, current state, what to change, what to leave untouched, the project's actual gates, and a report contract. Tell omp not to commit, and keep one task per brief. omp auto-loads AGENTS.md/CLAUDE.md context files from the workspace and its parents, so repo instructions reach it without inlining them.
2. Dispatch through the bundled relay, which pipes the brief to omp --mode json on stdin, captures the JSON event stream, and writes result.json. The child process's cwd pins the workspace; the relay writes artifacts under the system temp dir and never commits.
3. Wait for completion. The relay blocks until omp finishes, or it can be backgrounded and polled for result.json. A pre-run usage error exits 2 and writes no result; a missing omp binary exits 127 and writes status: "omp_unavailable". Trust process state and the working tree over any progress display - completion means the process exited and result.json exists. omp's full report is the finalMessage field in result.json.
4. Review - don't trust the self-report. Treat omp's final message and gate claims as claims, not facts: re-run the project's gates, read the diff against the brief starting with touchedFiles, run relevant guard skills if installed, and round-trip migrations plus grep for dangling references after removals or renames.
5. Land it. The implementer edits the working tree; the orchestrator commits, only after the gates pass and the diff holds. Rework goes back through a delta brief with --resume-last or --session <id>, then review again.

Use it to delegate a bounded coding task and review the diff afterward, or when explicitly asked to delegate to Oh My Pi specifically.

Do NOT use it when the task is small enough to do inline (delegation overhead outweighs the benefit), when the omp CLI is not installed or authenticated, when the user asked for the original Pi CLI (use pi-delegate instead), or when a sandboxed implementer is required - Oh My Pi has no sandbox. --read-only restricts the tool surface to --tools read,grep,glob; a write-capable run executes without prompts via --yolo.

Prerequisites: install with bun install -g @oh-my-pi/pi-coding-agent (or the install path from omp.sh), authenticate via /login inside omp for a subscription provider or an API-key environment variable for an API-key provider (credentials live under ~/.omp/), confirm omp --version succeeds, and work in or point --cd at the target git repository.

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

Model selection is optional - omitting --model/--provider uses omp's configured default. To choose another model, list what the install can run with omp models (or omp models --json, or omp models find <substring>, or omp models <provider>) - never omp --list-models, which is removed and exits 2 as an unknown flag. Pass the id via --model <pattern>, a fuzzy match against the catalog, with --provider <name> to pin the provider when the pattern is ambiguous. The relay forwards only letters, digits, and . _ : / -; glob patterns with * are rejected. --thinking <level> is a separate reasoning dial (off, auto, minimal, low, medium, high, xhigh, max) - the relay rejects anything else, including inherit, before dispatch. A fleet lane's --lane flag can set provider, model, and effort (effort becomes --thinking); an explicit flag on the call always wins over the lane. The relay does not forward --api-key, --smol, --slow, or --plan - those stay omp's own CLI flags.

Output is result.json, holding the JSON event stream and the finalMessage field with omp's full report (also printed between report markers on stdout), plus touchedFiles listing what changed.

Oh My Pi has no sandbox. Print mode has no approval UI, so a write-capable relay run always passes --yolo (tools.approvalMode: yolo) - otherwise a user's always-ask or write config would stall until the watchdog. --read-only restricts callable tools without passing --yolo, though installed extension code still runs with the user's host permissions if project resources are trusted. The relay passes --no-extensions --no-skills --no-rules by default, so project .omp extensions, skills, and rules stay undiscovered unless --approve opts in for a trusted repository. Delegation is something the human opts into; once granted ("run this queue", "proceed"), committing verified, gate-passing work is the agreed contract - within two limits: surface, don't absorb (report omp's design decisions and non-blocking nitpicks rather than silently accepting them) and stop for scope changes (ask instead of expanding the mandate if correct completion needs going beyond the brief).

Orchestrating agents or developers who want to delegate a bounded coding task to a separate Oh My Pi implementer session while keeping review and commit authority themselves.