Turn On Direct Worker Dispatch

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

First time using AIWG? Begin with Install, Connect, and Verify.

What it does

AIWG can dispatch bounded pieces of work directly to other AI CLIs installed on your machine (for example Codex or Muse), instead of only delegating inside the single provider session you are talking to. This is controlled by one setting: `parallelism.worker_dispatch` in `.aiwg/aiwg.config`. It is off by default.

When it is off, AIWG's model-selected delegation rubric still applies — the active provider delegates to its own native subagents. When it is on, AIWG can also place work directly onto other configured worker CLIs.

What it costs

Direct dispatch uses your other accounts' quota. If AIWG dispatches a task to Codex or Muse, that run consumes that tool's own API/account usage — not the provider session you started from. Review the parallelism caps and worker configuration before enabling it on a shared or metered account.

How AIWG offers it

the agent-owned init operation and the agent-owned setup operation detect which supported worker CLIs are installed (a fast, local, presence-only check — no network call and nothing is spawned). When two or more are detected and dispatch is off, the setup step asks one yes/no question naming the detected CLIs. The default answer is no: nothing is enabled without an explicit yes at a terminal, or an explicit config command.

Until you answer, or whenever the question can't be asked (non-interactive runs, CI, dry runs), the agent-owned regenerate operation, the agent-owned refresh operation, and the agent-owned doctor operation print a single reminder line instead (naming the enable command) when dispatch is still off and two or more worker CLIs are detected.

If you say no, AIWG remembers the decline (`setup.worker_dispatch_offer: "declined"` — a setup preference, kept separate from the worker-policy settings above) and stops offering it entirely: the question is not asked again, and none of the reminder lines above print anymore either. The generated project context also reflects the decline so agents don't keep re-offering it. To change your mind later, just run the enable command below directly — turning dispatch on always takes priority over a recorded decline, so there is no separate "undo the decline" step.

How to turn it on

Use AIWG to complete this documented outcome: How to turn it on
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Then confirm the CLIs AIWG would dispatch to are actually installed and launchable:

Use AIWG to complete this documented outcome: Then confirm the CLIs AIWG would dispatch to are actually installed and launchable
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

How to turn it off

Use AIWG to complete this documented outcome: How to turn it off
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Turning it off only changes this one setting — any per-CLI enablement (`parallelism.clis`) and group configuration keep their existing values, so turning dispatch back on later restores the same setup.