OpenClaw-first orchestration CLI for tracked, multi-agent execution.

Zigrix turns ad-hoc delegation into a visible workflow with specialist routing, evidence collection, and reportable finalization.

Why Zigrix · Is Zigrix for you? · Quick Start · Core Workflow · OpenClaw Integration · Dashboard · Docs

Most agent-heavy workflows break down in the same places:

• work gets delegated, but not consistently tracked
• specialist routing depends on memory, not policy
• outputs arrive without structured evidence
• final reporting is manual and hard to audit

Zigrix gives that flow a control surface: dispatch, worker lifecycle, evidence, and finalization in one runtime.

Zigrix is a strong fit if you want:

• one-time operator setup, then agent-driven execution
• repeatable orchestration rules instead of ad-hoc delegation
• recoverable local runtime state for task progress and reports
• OpenClaw compatibility without requiring a plugin-based architecture

Zigrix may be a poor fit if your main goal is a hosted, multi-tenant control plane.

• Operating systems: macOS, Linux
• Runtime: Node.js (current LTS recommended)
• Package manager: npm
• OpenClaw: optional, but recommended for full orchestration flow

Zigrix still works as a standalone CLI when OpenClaw is not installed.

npm install -g zigrix

From source:

./install.sh

zigrix onboard

zigrix doctor
zigrix dashboard

That is the intended entry flow: install → onboard → done.

This split keeps normal operation agent-driven while keeping setup and governance human-controlled.

Typical operational flow:

Human setup
  install -> zigrix onboard -> doctor check

Agent execution
  zigrix task dispatch
    -> worker prepare/register/complete
    -> evidence collect/merge
    -> task finalize + report

Common commands:

# Dispatch orchestration work
zigrix task dispatch --title "Implement auth module" --description "..." --scale normal --json

# Check runtime health
zigrix doctor

# Launch dashboard
zigrix dashboard --port 3838

# Maintenance surfaces
zigrix configure --section agents
zigrix configure --section skills
zigrix reset state --yes

zigrix onboard prepares runtime and integration in one pass:

1. creates runtime directories from zigrix.config.json (paths.*) and default config/state structure
2. seeds rule files from bundled templates
3. ensures zigrix is reachable from the runtime-visible PATH
4. detects OpenClaw and imports agents from openclaw.json
5. registers bundled skills/zigrix-* into ~/.openclaw/skills/
6. leaves the environment ready for agent-led orchestration

When OpenClaw is present, Zigrix is optimized for this model:

• import agent definitions and normalize roles
• establish orchestrator ownership for task execution
• register Zigrix skill packs for agent readiness checks
• keep CLI reachability stable for OpenClaw runtime

Read the full integration contract in docs/openclaw-integration.md.

Zigrix ships with a built-in dashboard for real-time visibility into task orchestration.

zigrix dashboard --port 3838

Track execution units, evidence submissions, and spec previews — all in one view.

Every state change is recorded as an immutable event — from dispatch through finalization.

Monitor in-progress tasks with real-time execution unit status and one-click cancellation.

Full task specification with metadata, scope definition, and routing rules — visible before and during execution.

• Quickstart
• Install
• OpenClaw Integration
• CLI Spec
• Architecture
• Troubleshooting

See CONTRIBUTING.md.

See SUPPORT.md.

See SECURITY.md.

Apache-2.0