nuro-omp

A decomposed multi-agent coding harness — pure config on top of Oh My Pi (omp).

nuro-omp turns a single omp session into a disciplined team: one Conductor (your main session) that spawns six specialized sub-agents — architect, builder, builder-max, tester, reviewer, scout — governed by a small set of rules (smart-zone context budgets, vertical slices, a 3-try test gate with model escalation, and a repo-resident memory bundle). No orchestration server, no fork of omp — just markdown agents + YAML config that omp reads natively.

⚠️ Early release (v0.1). The global install below works today on macOS, Linux, and Windows. omp runs on the Bun runtime — Bun is required (Node alone can install nuro-omp but cannot run omp). Standalone download-and-run binaries are experimental (see scripts/build-binaries.sh). Follow START-HERE.md for the full path.

What's in here

| Path | What it is | |---|---| | AGENTS.md | The project router — every session reads this first | | .omp/ | The 6 agents, 8 skills, model config, team protocol | | templates/ | Provider config (keymux/local proxy, GLM) + SHIP.template.md — the scope-stop each project copies (human-owned) | | docs/ | PROVIDERS.md — how to connect models (subscriptions, API keys, local proxies) | | START-HERE.md | Top-to-bottom launch guide |

Requirements

• Bun — required (omp is a Bun program; Node cannot run it). Install: curl -fsSL https://bun.sh/install | bash (macOS/Linux) or powershell -c "irm bun.sh/install.ps1 | iex" (Windows)
• Node ≥ 18 or Bun to run the npm/bun install (the install pulls the pinned omp @16.3.6 automatically)
• A model provider: a subscription (Claude/GLM/Gemini via /login), an API key, or any Anthropic-compatible proxy (see docs/PROVIDERS.md)
• macOS / Linux / Windows

Quick start

# 1. Bun is the omp runtime — install it first if you don't have it:
curl -fsSL https://bun.sh/install | bash        # Windows: powershell -c "irm bun.sh/install.ps1 | iex"

npm install -g nuro-omp      # or: bun install -g nuro-omp
nuro-omp                     # you are the Conductor — works in any directory
/login anthropic             # connect a model

nuro-omp installs a harness profile (~/.omp/profiles/nuro/agent/) and runs omp against it — the six agents + skills + config travel with the profile, so you never copy config into your projects. No fork of omp; pure profile injection.

See START-HERE.md for the full path — install → connect models → first-run → daily-use.

Why it's built this way

A single all-purpose agent drifts: it holds too much in context, writes past "done," and has no one checking its work. nuro-omp splits that one agent into a small team with sharp edges, because each constraint fixes a specific failure:

• One Conductor + specialized sub-agents. The main session never writes code — it plans and delegates. Each sub-agent (architect, builder, tester, reviewer, scout) starts fresh with only the context its job needs, so no single agent carries the whole world and loses focus.
• Vertical slices, not big-bang changes. Work ships in ≤5-file slices that each stand on their own. Small blast radius means every step is reviewable and reversible.
• A 3-try test gate with model escalation. Code isn't "done" because it was written — it's done when tests pass. Try 1–2 use the fast model; a stuck slice escalates to a stronger model (builder-max) before it ever reaches you. Failure is bounded, not open-ended.
• A repo-resident memory bundle. Decisions and context live in the repo, not in a chat that evaporates — so the next session (human or agent) picks up where the last one left off.
• A scope-stop (SHIP.md). One human-owned file defines "done" and what the project will not do, so the team ships instead of gold-plating forever.

The mechanism is deliberately boring: no orchestration server, no fork of omp, no plugins — just markdown agents and YAML config that omp reads natively. That's what makes it portable and easy to trust.

License

MIT — see LICENSE.