Manta Orchestration
This file is a discovery stub, not the usage guide. The full, version-matched Manta
orchestration reference is served by the manta binary itself — kept out of this file on
purpose so it can never drift from the binary that will actually run your commands.
Engage Manta 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 manta-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 Manta runtime
state; never substitute a non-Manta subagent tool.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
MANTA_CLI_COMMAND environment variable is set, use its value. Manta exports this
for managed WSL sessions.
- Otherwise, in a dev checkout whose session exposes
MANTA_DEV_REPO_ROOT, use manta-dev.
- Otherwise, on Linux outside a Manta-managed terminal, use
manta-ide. Never run bare
manta there — outside Manta's terminals it normally resolves to the
GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine.
- Otherwise, use
manta.
Below, MANTA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run MANTA 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 Manta build.
Load the version-matched guide before running Manta commands
MANTA skills get orchestration
That prints the compact, version-matched guide for the exact binary that will handle your
next commands. It covers the normal local coordinator loop. For a conditional action gate
such as remote placement, uncertain release recovery, or expanded DAG work, load only the
reference that gate names with
MANTA skills get orchestration --reference references/<file>.md
(--references lists the names). If that binary rejects --reference, run
MANTA skills get orchestration --full and read the named bundled reference before acting.
Prefer --json. Use the selected executable's --help for commands or flags the guide does
not cover. If a command reports that Manta is not running, start it with MANTA open --json
and retry. If skills get is unknown, explain that updating Manta restores the guide; use
--help for read-only discovery and do not guess unsupported commands.
1---2name: orchestration3description: Coordinate supervised Manta workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and decomposing work across agents. Use `manta-cli` for full ownership handoffs — "hand off", "handoff", "handover", "give this to another agent", "another worktree" — unless asked to supervise, monitor, or coordinate a DAG, and for terminal control, lightweight terminal prompts, shell commands, Manta worktree management, and reading or waiting on terminals. Use Computer Use for external browser windows, webviews, Manta app UI, or desktop UI outside Manta's embedded browser only when the task requires OS/window-level control such as focus, menus, dialogs, coordinates, or screenshots. Use `manta-cli` for Manta's embedded pages and a page-automation tool such as Playwright or CDP for external pages.4---56# Manta Orchestration78This file is a discovery stub, not the usage guide. The full, version-matched Manta9orchestration reference is served by the `manta` binary itself — kept out of this file on10purpose so it can never drift from the binary that will actually run your commands.1112Engage Manta orchestration whenever you need structured multi-agent coordination: threaded13messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs,14decision gates, coordinator loops, or decomposing work across agents. Use the manta-cli skill15instead for full ownership handoffs ("hand off", "handoff", "handover", "give this to16another agent", "another worktree") when the user did not ask to supervise, monitor, wait17for results, or coordinate a DAG — and for ordinary terminal control, shell commands,18worktree management, and the built-in browser. Coordination requires real Manta runtime19state; never substitute a non-Manta subagent tool.2021## Resolve the CLI for this session2223Choose the executable once and reuse it for every later command:2425- If the `MANTA_CLI_COMMAND` environment variable is set, use its value. Manta exports this26 for managed WSL sessions.27- Otherwise, in a dev checkout whose session exposes `MANTA_DEV_REPO_ROOT`, use `manta-dev`.28- Otherwise, on Linux outside a Manta-managed terminal, use `manta-ide`. Never run bare29 `manta` there — outside Manta's terminals it normally resolves to the30 GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine.31- Otherwise, use `manta`.3233Below, `MANTA` is a placeholder for the executable you resolved. Substitute it before34running anything; do not create a shell variable or run `MANTA` literally. This works the35same way in POSIX shells, PowerShell, and cmd.exe.3637If the selected executable cannot run, report its exact error and stop. Do not fall through38to another executable, which could silently target a different Manta build.3940## Load the version-matched guide before running Manta commands4142```text43MANTA skills get orchestration44```4546That prints the compact, version-matched guide for the exact binary that will handle your47next commands. It covers the normal local coordinator loop. For a conditional action gate48such as remote placement, uncertain release recovery, or expanded DAG work, load only the49reference that gate names with50`MANTA skills get orchestration --reference references/<file>.md`51(`--references` lists the names). If that binary rejects `--reference`, run52`MANTA skills get orchestration --full` and read the named bundled reference before acting.5354Prefer `--json`. Use the selected executable's `--help` for commands or flags the guide does55not cover. If a command reports that Manta is not running, start it with `MANTA open --json`56and retry. If `skills get` is unknown, explain that updating Manta restores the guide; use57`--help` for read-only discovery and do not guess unsupported commands.
paidaxingyo666