OpenNexum

---

name: opennexum

version: 2.1.2

description: Contract-driven multi-agent orchestration with ACP. Webhook + dispatch-queue dual dispatch, cross-review, auto-retry, batch progress tracking.

requires:

node: ">=20"

tools: [pnpm, openclaw]

---

# OpenNexum

Contract-driven coding agent orchestration via OpenClaw ACP.

When to use

Architecture

Dispatch (dual-path)

1. **Webhook (real-time)**: `nexum callback` → POST `/hooks/agent` → orchestrator wakes up immediately

2. **Dispatch Queue (fallback)**: `nexum callback` → writes `nexum/dispatch-queue.jsonl` → heartbeat processes within 10min

Cross-review

Auto-routing

Batch progress

Agent Naming: `<model>-<role>-<number>`

Key CLI Commands

nexum init [--project <dir>] [--yes]
nexum spawn <taskId> [--project <dir>]
nexum track <taskId> <sessionKey>
nexum callback <taskId> [--role evaluator] [--model gpt-5.4] [--input-tokens N] [--output-tokens N]
nexum eval <taskId>
nexum complete <taskId> <pass|fail|escalated>
nexum status [--project <dir>]
nexum archive [--project <dir>]
nexum health [--project <dir>]
nexum retry <taskId> --force

Contract YAML

id: TASK-001
name: "implement feature X"
batch: batch-1
agent:
  generator: codex-gen-01
  evaluator: claude-eval-01
scope:
  files:
    - src/feature.ts
deliverables:
  - path: src/feature.ts
    description: "..."
eval_strategy:
  type: review
  criteria:
    - id: C1
      desc: "..."
      weight: 2
max_iterations: 3

Callback Protocol (injected into AGENTS.md via nexum init)

After completing a task, run:

nexum callback <taskId> --project <projectDir> \
  --model gpt-5.4 \
  --input-tokens <n> \
  --output-tokens <n>

Git Convention