Contract-driven coding agent orchestration via OpenClaw ACP.
nexum callback → POST /hooks/agent → orchestrator wakes up immediatelynexum callback → writes nexum/dispatch-queue.jsonl → heartbeat processes within 10mingenerator: auto in Contract YAML → system selects agent by task typenexum status shows current batch progress + overall progress-- nexum init [--project <dir>] [--yes]
nexum sync [taskId] [--project <dir>]
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
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
nexum init writes the callback protocol into AGENTS.md as the source of truth. If a project only has CLAUDE.md, Nexum will seed AGENTS.md from it and update AGENTS.md going forward.
After completing a task, run:
nexum callback <taskId> --project <projectDir> \
--model gpt-5.4 \
--input-tokens <n> \
--output-tokens <n>
main, revert if neededfeat(scope): TASK-ID: description共 1 个版本