orchestrator: Skill for Claude Code

Agent Orchestrator Guide

CLI Command Reference (Dynamic)

Before reading static documentation, query the orchestrator itself:

orchestrator guide                         # full categorized command reference
orchestrator guide task                    # filter by command name
orchestrator guide --category resource     # filter by category
orchestrator guide --format json           # machine-readable output

The guide subcommand outputs up-to-date command descriptions with usage examples, grouped by functional category. Use it as your primary CLI reference.

Architecture (Client/Server)

The orchestrator uses a client/server model over gRPC:

• orchestratord — daemon binary (gRPC server + embedded worker pool). Listens on UDS (~/.orchestratord/orchestrator.sock) by default, or TCP with --bind.
• orchestrator — thin CLI client binary that forwards all commands to the daemon via gRPC.

Install via the one-line installer or download from GitHub Releases:

curl -fsSL https://raw.githubusercontent.com/c9r-io/orchestrator/main/install.sh | sh

Start the daemon first, then use the CLI:

# Start daemon (standalone binary, not a CLI subcommand)
orchestratord --foreground --workers 2           # foreground (recommended for monitoring)
nohup orchestratord --foreground --workers 2 &   # background via nohup
orchestratord --bind 0.0.0.0:9090 --workers 4   # TCP instead of UDS

# Monitor daemon
ps aux | grep orchestratord | grep -v grep       # check process

# Stop daemon
kill <pid>                                        # graceful SIGTERM

Core Workflow

1. Start the daemon: orchestratord --foreground --workers 2
2. orchestrator init — initialize orchestrator runtime (creates ~/.orchestratord/ with DB, secrets, etc.)
3. orchestrator apply -f manifest.yaml --project <name> — load resources (daemon atomically hot-reloads an ArcSwap config snapshot, no restart needed)
4. orchestrator task create --name X --goal Y --workflow Z --project <name> — create and run (auto-enqueues to worker)
5. orchestrator task info <id> / task trace <id> / task logs <id> — inspect results