# Orchestration

> Use h0x-ADE orchestration for structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, decision gates, or coordinator loops. Use `orca-cli` instead for full ownership handoffs, including requests phrased as "hand off", "handoff", "handover", "give this to another agent", or "another worktree" when the user did not explicitly ask to supervise, monitor, wait for results, or coordinate a DAG. Use `orca-cli` for terminal control, lightweight terminal prompts, shell commands, h0x-ADE worktree management, reading or waiting on terminals, and the h0x-ADE embedded browser. Use Computer Use for external browser windows, webviews, h0x-ADE app UI, or desktop UI outside h0x-ADE's embedded browser only when the task requires OS/window-level control such as focus, menus, dialogs, coordinates, or screenshots. Use `orca-cli` for h0x-ADE's embedded pages and a page-automation tool such as Playwright or CDP for external pages.

- Skill: `vjk7989/orchestration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vjk7989/orchestration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vjk7989/orchestration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: vjk7989 (https://skillmd.com/u/vjk7989)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vjk7989/orchestration

---


# h0x-ADE Orchestration

This file is a discovery stub, not the usage guide. The full, version-matched h0x-ADE
orchestration reference is served by the `h0x` binary itself — kept out of this file on
purpose so it can never drift from the binary that will actually run your commands.

Engage h0x-ADE orchestration whenever you need structured multi-agent coordination: threaded
messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs,
decision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill
instead for full ownership handoffs ("hand off", "handoff", "handover", "give this to
another agent", "another worktree") when the user did not ask to supervise, monitor, wait
for results, or coordinate a DAG — and for ordinary terminal control, shell commands,
worktree management, and the built-in browser. Coordination requires real h0x-ADE runtime
state; never substitute a non-h0x-ADE subagent tool.

## Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. h0x-ADE exports this
  for managed WSL sessions.
- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `h0x-dev`.
- Otherwise, use `h0x`.

Below, `H0X` is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run `H0X` literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.

If the selected executable cannot run, report its exact error and stop. Do not fall through
to another executable, which could silently target a different h0x-ADE build.

## Load the full guide before running h0x commands

```text
H0X skills get orchestration
```

That prints the complete, version-matched guide for the exact binary that will handle your
next commands — task creation and dispatch, injected lifecycle preambles, worker_done
authority, decision gates, and coordinator loops. Read it first, then run the specific
command you need.

Don't guess subcommands or flags from memory or from a cached copy of this stub. They
change between h0x-ADE releases, and this file deliberately no longer lists them. Confirm the
app is up with `H0X status --json` (start it with `H0X open --json` if needed), and
prefer `--json` for agent-driven calls.

## If an older installation does not recognize `skills get`

Use this fallback only when the selected binary explicitly reports that `skills get` is an
unknown command. Another failure is not proof of an older binary; report it rather than
guessing or changing executables. For a confirmed pre-guide binary, use only this bounded,
read-only bootstrap to orient. Do not dead-end and do not invent commands:

```text
H0X status --json
H0X orchestration task-list --json
H0X terminal list --json
```

Then tell the user that updating h0x-ADE restores the full, version-matched guide via
`H0X skills get orchestration`. Beyond these commands, ask the user rather than guessing a
command surface this older binary may not support.